Linear (API key) ACTION
List Project Updates
List project updates in Linear, optionally scoped to a single project. Use List Projects to find a project ID. Returns update objects with
id, body, health, createdAt, and author. Example: projectId: "a1b2c3d4-0000-0000-0000-000000000001", first: 10 → returns {nodes: [{id: "pu_01xyz", body: "Q3 milestone complete.", health: "onTrack"}], pageInfo: {endCursor: "...", hasNextPage: false}}. See the documentation.- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Linear (API key) account once, then configure and run List Project Updates 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: "linear_app-list-project-updates",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
linear_app: { authProvisionId: "apn_xxxxxxx" },
projectId: "Project",
orderBy: "Order By",
},
})
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": "linear_app-list-project-updates",
"configured_props": {
"linear_app": { "authProvisionId": "apn_xxxxxxx" },
"projectId": "Project",
"orderBy": "Order By"
}
}'// 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": "linear_app",
},
},
},
)
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: "linear_app-list-project-updates",
arguments: {
projectId: "Project",
orderBy: "Order By",
},
})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 |
|---|---|---|
projectId Project | string | The ID of the project to scope updates to (a UUID, e.g. a1b2c3d4-0000-0000-0000-000000000001). Run List Projects first to obtain a valid project ID. Leave blank to list updates across all accessible projects. Optional |
orderBy Order By | string | By which field should the pagination order by. Available options are createdAt (default) and updatedAt. Optional |
first First | integer | Maximum number of records to return (min 1, max 100). Example: 10. Optional |
after After | string | Pagination cursor from a previous response's pageInfo.endCursor to fetch the next page. Example: 4919b279-3121-4609-880e-a70c11deca5a. Optional |
fields Fields | string[] | Optional list of field names to include in each returned project update object. When omitted, the full payload is returned. Pass a subset to reduce response size, e.g. ["id", "body", "health"]. 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
- linear_app-list-project-updates
- Version
- 0.0.1
- App
- Linear (API key)
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗