Skip to main content
Glama

linear_updateReleaseStage

Idempotent

Update an existing release stage by providing its ID and modifying fields like name, color, frozen status, or position.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the release stage to update
nameNoThe updated stage name
colorNoThe updated UI color as a HEX string
frozenNoWhether the started stage should be frozen
positionNoThe updated stage position

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
typeNo
colorNo
frozenNo
pipelineNo
positionNo
createdAtNo
updatedAtNo
archivedAtNo
descriptionNo
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description's update semantics are consistent. The description adds the requirement of at least one change field but does not elaborate on side effects or authorization. This is adequate but not exceptional.

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 sentence of 12 words, front-loading the action. It is highly concise without unnecessary detail.

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?

The tool has an output schema (not shown) so return values need not be explained. The description covers the essential behavior. It could mention when to use this tool versus create/archive/deletion but the sibling names provide context. Slightly incomplete but functional.

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% with descriptions for each parameter. The description adds the rule that at least one non-id field must be provided, which is not in the schema's required list. This additional constraint improves semantic understanding.

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?

The description 'Update an existing release stage' clearly specifies the action (update) and resource (release stage). Among siblings like linear_updateRelease and linear_updateReleasePipeline, it uniquely identifies this tool's 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?

The description provides a clear guideline: 'Provide id plus at least one other field to change.' This tells the agent the minimum input needed. It lacks explicit when-not-to-use or alternatives, but the guideline is valuable.

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