Linear (API key) ACTION
List Views
List saved custom views in Linear. Use this to discover valid view IDs for the Get View Issues action. Custom views combine filters (team, assignee, state, labels, etc.) into a reusable saved search. Optionally filter by team. Example:
teamId: "9d1c3f7e-..." → returns {nodes: [{id: "cv1abc", name: "My Open Issues", teamId: "9d1c3f7e-..."}], 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 Views 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-views",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
linear_app: { authProvisionId: "apn_xxxxxxx" },
teamId: "Team",
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-views",
"configured_props": {
"linear_app": { "authProvisionId": "apn_xxxxxxx" },
"teamId": "Team",
"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-views",
arguments: {
teamId: "Team",
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 |
|---|---|---|
teamId Team | string | Filter views by team. Use Get Teams to discover valid team IDs. Optional |
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 views to return Optional |
after After | string | The cursor to return the next page of views Optional |
fields Fields | string[] | Optional list of field names to include in each returned view object. When omitted, the full view payload is returned. Pass a subset to reduce response size, e.g. ["id", "name"]. 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-views
- Version
- 0.1.0
- App
- Linear (API key)
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗