Linear (API key) ACTION
List Labels
List issue labels in the Linear workspace. Use this to discover valid label names and IDs for creating or filtering issues. Returns label objects with
id, name, and color. Example: first: 50 → returns {nodes: [{id: "lbl_bug123", name: "Bug", color: "#ef4444"}, {id: "lbl_fe456", name: "Frontend", color: "#0ea5e9"}], 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 Labels 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-labels",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
linear_app: { authProvisionId: "apn_xxxxxxx" },
orderBy: "Order By",
first: 10,
},
})
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-labels",
"configured_props": {
"linear_app": { "authProvisionId": "apn_xxxxxxx" },
"orderBy": "Order By",
"first": 10
}
}'// 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-labels",
arguments: {
orderBy: "Order By",
first: 10,
},
})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 |
|---|---|---|
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 labels to return Optional |
after After | string | Cursor for pagination to fetch the next page (example: "label_01J8XYZABCDEF123456789"). Optional |
before Before | string | Cursor for pagination to fetch the previous page (example: "label_01J8XYZABCDEF123456789"). Optional |
last Last | integer | The number of items to backward paginate (used with before). Defaults to 50. Optional |
includeArchived Include archived | boolean | Should archived resources be included? (default: false) Optional |
filter Filter | object | Filter returned issue labels. See the documentation for more details. Example: { "name": { "contains": "Bug" } } Optional |
fields Fields | string[] | Optional list of field names to include in each returned label object. When omitted, the full label payload is returned. Pass a subset to reduce response size, e.g. ["id", "name", "color"]. 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-labels
- Version
- 0.1.0
- App
- Linear (API key)
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗