Skip to main content
Glama

linear_updateReleasePipeline

Idempotent

Update a Linear release pipeline's properties by specifying its ID and the fields to modify.

Instructions

Update an existing release pipeline. Provide id plus at least one other field to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the release pipeline to update
nameNoThe updated pipeline name
typeNoThe updated pipeline type
slugIdNoThe updated pipeline slug identifier
teamIdsNoThe updated team identifiers for the pipeline
isProductionNoWhether the pipeline targets production
includePathPatternsNoUpdated glob patterns to include matching commit paths

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
nameNo
typeNo
teamsNo
slugIdNo
stagesNo
createdAtNo
updatedAtNo
archivedAtNo
productionNo
descriptionNo
pathPatternsNo
latestReleaseNoteNo
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false. Description adds behavioral constraint that at least one other field must be provided, which is useful. No contradiction with annotations. Could have mentioned idempotency explicitly but annotations cover it.

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?

Two sentences with no unnecessary words. Information is front-loaded: the core action and a key constraint are stated immediately.

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

Completeness4/5

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

With full schema coverage, annotations, and output schema present, the description adequately covers the essentials. It could mention idempotency or return value details, but these are covered by annotations and output schema.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds the requirement that at least one field besides id must be changed, which adds meaning beyond the schema. This guideline is not apparent from schema alone.

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?

Clearly states verb 'Update' and resource 'release pipeline'. Distinguishes from siblings like linear_updateRoadmap by specifying the exact resource. The requirement 'Provide id plus at least one other field' further clarifies purpose.

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

Usage Guidelines4/5

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

Explicitly states the requirement that id plus at least one other field must be provided. This is a clear usage guideline. Does not explicitly contrast with alternatives, but the context of sibling tools (e.g., linear_archiveReleasePipeline) makes it implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tacticlaunch/mcp-linear'

If you have feedback or need assistance with the MCP directory API, please join our Discord server