Linear ACTION
Update Issue
Updates an existing Linear issue. Can modify title, description, assignee, state, project, team, labels, priority, and dates. Returns updated issue details. Uses OAuth authentication. See Linear docs for additional info here.
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Linear account once, then configure and run Update Issue 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-update-issue",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
linear: { authProvisionId: "apn_xxxxxxx" },
teamId: "Current Team",
issueId: "Issue",
},
})
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-update-issue",
"configured_props": {
"linear": { "authProvisionId": "apn_xxxxxxx" },
"teamId": "Current Team",
"issueId": "Issue"
}
}'// 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",
},
},
},
)
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-update-issue",
arguments: {
teamId: "Current Team",
issueId: "Issue",
},
})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 |
|---|---|---|
teamId Current Team | string | The identifier or key of the team associated with the issue Required Dynamic |
issueId Issue | string | The issue to update Required Dynamic |
title Title | string | The title of the issue. Optional |
description Description | string | The issue description in markdown format Optional |
teamIdToUpdate Team | string | The identifier or key of the team to update the issue to Optional Dynamic |
stateId State (Status) | string | The state (status) to assign to the issue Optional Dynamic |
assigneeId Assignee | string | The user to assign to the issue Optional Dynamic |
labelIds Issue Labels | string[] | The labels in the issue Optional Dynamic |
projectId Project | string | The identifier or key of the project associated with the issue Optional Dynamic |
priority Priority | integer | The priority of the issue 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-update-issue
- Version
- 0.1.16
- App
- Linear
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗