MCP Linear

linear_getReleaseNotes

Read-onlyIdempotent

Retrieve release notes from Linear. Filter by creation or update date, limit results, and include archived notes to access project updates.

Instructions

Get release notes from Linear

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of release notes to return (default: 25)
`orderBy`	No	Sort release notes by created or updated date
`includeArchived`	No	Include archived release notes 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.3/5.0

Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds no behavioral details beyond the verb 'Get'. No contradiction with annotations.

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

Conciseness5/5

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

The description is a single, efficient sentence with no filler words. Every word adds value without being verbose.

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 tool's simplicity (3 optional parameters, no required), the description is minimally complete. However, it could better clarify the scope relative to sibling tools and what constitutes a release note.

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?

All three parameters have descriptions in the input schema, achieving 100% schema description coverage. The tool's description does not add any additional meaning beyond what the schema provides.

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 tool retrieves release notes from Linear, using a specific verb and resource. However, it does not differentiate itself from the sibling tool linear_getReleaseNoteById, which retrieves a single note.

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 like linear_getReleaseNoteById or linear_getReleases. The description lacks context on typical use cases 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