Skip to main content
Glama

linear_updateCustomerNeed

Idempotent

Update an existing customer need in Linear by modifying its body, priority, linked issue or project, and attachment URL.

Instructions

Update a customer need

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCustomer need ID
bodyNoUpdated need content in Markdown
issueIdNoIssue ID linked to the need
priorityNoNeed priority: 0 not important, 1 important
projectIdNoProject ID linked to the need
customerIdNoLinear customer ID
attachmentUrlNoUpdated attachment URL
customerExternalIdNoExternal customer ID
applyPriorityToRelatedNeedsNoApply priority changes to related needs on the same issue or project

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
bodyNo
issueNo
contentNo
creatorNo
issueIdNo
projectNo
customerNo
priorityNo
commentIdNo
createdAtNo
projectIdNo
updatedAtNo
archivedAtNo
customerIdNo
attachmentIdNo
originalIssueNo
originalIssueIdNo
projectAttachmentNo
updatedRelatedNeedsNo
Behavior2/5

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

Description only says 'Update', which implies mutation. Annotations already indicate it is not read-only and not destructive. The description adds no additional behavioral context (e.g., side effects, permissions, rate limits).

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

Conciseness3/5

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

The description is extremely short (two words), which is concise but at the cost of completeness. It is not front-loaded with useful information; it is minimal.

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

Completeness2/5

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

Given the complexity (9 optional parameters, output schema exists), the description is too brief. It does not explain what the update returns, any side effects, or how to use related fields effectively. The output schema is present but not leveraged in the description.

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 9 parameters are described in the schema (100% coverage). The tool description does not add further meaning beyond the schema, so baseline of 3 is appropriate.

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?

Description clearly states 'Update a customer need', indicating the action and resource. It is straightforward, though it does not differentiate from sibling update tools like 'linear_updateCustomer'.

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 provided on when to use this tool versus alternatives, such as 'linear_createCustomerNeed' or 'linear_archiveCustomerNeed'. No exclusions or context given.

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