Linear (API key) ACTION
Search Issues
Search Linear issues by team, project, assignee, labels, state, or text query. Returns up to 200 matching issues (paginated internally). Use Get Teams for team IDs, List Projects for project IDs, List Workflow States for state IDs, List Users for assignee IDs, and List Labels for label names. Use the optional
fields prop to narrow the response to only the keys you need (reduces context size for large result sets). Example: teamId: "9d1c3f7e-...", query: "login redirect" → returns [{id: "iss_01", identifier: "ENG-42", title: "Fix login redirect on mobile", state: {name: "In Progress"}}]. 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 Search 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-search-issues",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
linear_app: { authProvisionId: "apn_xxxxxxx" },
teamId: "Team",
projectId: "Project",
},
})
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-search-issues",
"configured_props": {
"linear_app": { "authProvisionId": "apn_xxxxxxx" },
"teamId": "Team",
"projectId": "Project"
}
}'// 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-search-issues",
arguments: {
teamId: "Team",
projectId: "Project",
},
})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 issues by team (a UUID, e.g. 9d1c3f7e-2b48-4c6a-9f1e-5a7b8c9d0e1f). Leave this parameter out of the tool call entirely to search across all accessible teams — do not pass "*", an empty string, or any other placeholder, since only a real team UUID or no value at all are valid. Use Get Teams to discover valid team IDs. Optional |
projectId Project | string | The UUID of the project (e.g. a1b2c3d4-0000-0000-0000-000000000001). Use List Projects to find valid project IDs. Optional |
query Query | string | Search string to look for in issue titles. The query is used to filter issues where the title contains the query text (case insensitive). Optional |
stateId State (Status) | string | Filter issues by their workflow state (status). States are scoped to the selected team. Optional |
assigneeId Assignee | string | The UUID of the user to assign (e.g. abc12345-0000-0000-0000-000000000001). Use List Users to discover valid user IDs. Optional |
issueLabelNames Issue Labels | string[] | The label names to filter issues by (e.g. ["Bug", "Frontend"]). Use List Labels to find valid label names. Optional |
orderBy Order By | string | By which field should the pagination order by. Available options are createdAt (default) and updatedAt. Optional |
includeArchived Include archived | boolean | Should archived resources be included? (default: false) Optional |
limit Limit | integer | Maximum number of issues to return. If no query is provided, this defaults to 20 to avoid returning too many results. 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-search-issues
- Version
- 1.0.0
- App
- Linear (API key)
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗