Skip to main content
Glama

linear_createProjectUpdate

Create a new project update for a Linear project by providing the project ID, body content, and optionally the health status and diff hiding setting.

Instructions

Create a new project update for a Linear project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesBody content of the project update
healthNoOptional health status for the update
projectIdYesID of the project to create the update for
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 exist and are not contradicted. The description adds no behavioral context beyond creation, such as side effects or required permissions. With annotations present, score is adequate but uninspired.

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 sentence efficiently conveys the core purpose. No wasted words, but could be restructured to front-load key info. Minor room for improvement.

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?

Minimally complete given output schema and full parameter coverage. However, lacks usage context and behavioral details that would make it more helpful.

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 description coverage is 100%. The description does not add meaning beyond what the schema already provides, so baseline score of 3 applies.

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 clearly states the verb 'Create', the resource 'project update', and the context 'for a Linear project'. It distinguishes from siblings like update, get, archive, etc.

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 on when to use this tool versus alternatives (e.g., update or get). No mention of prerequisites or scenarios where this tool is appropriate.

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