MCP Linear

linear_getReleasePipelines

Read-onlyIdempotent

Fetch release pipelines from Linear, with options to sort by creation or update date, limit the number of results, and include archived pipelines.

Instructions

Get release pipelines from Linear

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of release pipelines to return (default: 25)
`orderBy`	No	Sort release pipelines by created or updated date
`includeArchived`	No	Include archived release pipelines in the results

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.3Sep 24, 2026

TDQS

B3.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, clearly conveying safety. The description adds no additional behavioral context beyond what annotations already provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence. It is concise and front-loaded, but could be more explicit about the tool's role (listing vs. searching).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and annotations are rich, the description is adequate but minimal. It does not clarify pagination, filtering behavior, or how it differs from similar tools, which would be helpful for a list operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides complete descriptions for all three parameters (100% coverage), so the description does not need to add parameter info. It meets the baseline but does not enhance understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'release pipelines', making the tool's purpose understandable. However, it lacks differentiation from siblings like linear_searchReleases, which also retrieves releases but with search capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as linear_getReleasePipelineById or linear_searchReleases. The description does not mention context, prerequisites, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server