Linear (API key) ACTION
Get View Issues
Retrieve issues filtered by a saved custom view in Linear. Custom views encapsulate pre-configured filters (team, state, assignee, labels, etc.). Use List Views to find the view ID. Use the optional
fields prop to narrow the response to only the keys you need (reduces context for large result sets). Example: viewId: "cv1b2c3d4-..." → returns {nodes: [{id: "iss_01", identifier: "ENG-42", title: "Fix login", state: {name: "In Progress"}}], 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 Get View Issues 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-get-view-issues",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
linear_app: { authProvisionId: "apn_xxxxxxx" },
viewId: "Custom View",
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-get-view-issues",
"configured_props": {
"linear_app": { "authProvisionId": "apn_xxxxxxx" },
"viewId": "Custom View",
"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-get-view-issues",
arguments: {
viewId: "Custom View",
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 |
|---|---|---|
viewId Custom View | string | The UUID of the custom view (e.g. ca1b2c3d-0000-0000-0000-000000000008). Use List Views to find valid view IDs. Required |
orderBy Order By | string | By which field should the pagination order by. Available options are createdAt (default) and updatedAt. Optional |
first First | integer | The number of issues to return Optional |
after After | string | The cursor to return the next page of issues Optional |
fields Fields | string[] | Optional list of field names to include in each returned issue object. When omitted, the full issue payload is returned. Pass a subset to reduce response size, e.g. ["id", "identifier", "title", "state"]. 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-get-view-issues
- Version
- 0.1.0
- App
- Linear (API key)
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗