MCP Linear

linear_getReleases

Read-onlyIdempotent

Retrieve Linear releases with filters for pipeline, stage, and archived status, plus sort and limit options to target specific release data.

Instructions

Get releases from Linear with optional pipeline and stage filters

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of releases to return (default: 25)
`orderBy`	No	Sort releases by created or updated date
`stageId`	No	Filter releases by release stage ID
`pipelineId`	No	Filter releases by release pipeline ID
`includeArchived`	No	Include archived releases 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.4/5.0

Behavior2/5

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

Annotations already indicate read-only and idempotent. Description adds no new behavioral context beyond restating schema parameters (pipeline/stage filters). Missing pagination or rate limit info.

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?

Single concise sentence with no fluff. Could benefit from structure (e.g., listing filters) but efficient for its purpose.

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?

Adequate for a simple list tool with output schema. Missing pagination or default limit context beyond schema parameter. Not fully complete.

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?

Schema covers all 5 parameters with descriptions (100% coverage). Description only highlights pipeline and stage filters, adding no new meaning beyond schema.

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

Purpose5/5

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

Clear verb 'Get' and resource 'releases' with explicit mention of optional filters. Distinguishes from siblings like getReleaseById and searchReleases.

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

Usage Guidelines3/5

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

Implies usage for listing releases with filters, but no explicit when-to-use or alternatives. Could mention searchReleases for more flexible search.

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

Deploy Server