Writer ACTION
List Applications
List the no-code applications (agents) in your Writer workspace. Use this to see which saved agents exist and to resolve an agent's
id, then call Get Application to inspect its inputs and Run Application to run it. Handles an empty workspace gracefully (returns an empty list). Auto-paginates up to 200 applications. Example: to list the content-generation agents and see just their names, call with type="generation" and fields=["name"] -> returns records like { id: "...", name: "Blog Writer" }. See the documentation- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Writer account once, then configure and run List Applications from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "writer-list-applications",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
writer: { authProvisionId: "apn_xxxxxxx" },
type: "Application Type",
fields: ["Fields"],
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "writer-list-applications",
"configured_props": {
"writer": { "authProvisionId": "apn_xxxxxxx" },
"type": "Application Type",
"fields": ["Fields"]
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "writer",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "writer-list-applications",
arguments: {
type: "Application Type",
fields: ["Fields"],
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
type Application Type | string | Filter by application type. generation for content-generation agents or research for research agents. Defaults to generation when omitted. Optional |
fields Fields | string[] | Field names to return for each application ( id is always included). Defaults to: name, type, status. Available fields include name, type, status, created_at, updated_at. Pass only what you need to keep responses small. Optional |
maxResults Max Results | integer | Maximum number of results to return. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- writer-list-applications
- Version
- 0.0.2
- App
- Writer
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗