Skip to main content
Glama

linear_updateProjectUpdate

Idempotent

Update the body, health status, or diff visibility of an existing project update in Linear.

Instructions

Update an existing project update in Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the project update to update
bodyNoUpdated body content of the project update
healthNoUpdated health status for the project update
isDiffHiddenNoWhether Linear should hide the diff against the previous project update

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
bodyNo
diffNo
userNo
healthNo
slugIdNo
projectNo
editedAtNo
createdAtNo
updatedAtNo
archivedAtNo
diffMarkdownNo
isDiffHiddenNo
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, providing safety profile. The description adds no extra behavioral context beyond 'Update', which is consistent but minimal.

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?

A single, front-loaded sentence contains the essential information with no unnecessary words. It is as concise as possible while conveying purpose.

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?

Given the presence of annotations and a full output schema, the description is sufficient for an update tool with few parameters. However, it does not mention required fields or common update patterns.

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 four parameters are described in the schema (100% coverage), and the description adds no additional meaning beyond what is already in the 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?

The description uses the specific verb 'Update' and resource 'project update', clearly indicating the action and distinguishing it from siblings like create, archive, or get.

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 explicit guidance on when to use this tool versus alternatives (e.g., create vs update, archive). The description only states what it does without contextualizing its role among siblings.

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