Skip to main content
Glama

linear_createCustomerNeed

Create a customer need linked to a Linear issue or project, specifying priority, body, and associated identifiers.

Instructions

Create a customer need linked to an issue or project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoNeed content in Markdown
issueIdNoIssue ID linked to the need
priorityNoNeed priority: 0 not important, 1 important
commentIdNoComment ID associated with the need
createdAtNoOptional creation timestamp (ISO 8601)
projectIdNoProject ID linked to the need
customerIdNoLinear customer ID
attachmentIdNoIssue attachment ID associated with the need
attachmentUrlNoAttachment URL for the need source
customerExternalIdNoExternal customer ID

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?

Annotations are neutral (no readOnly, destructive, or idempotent hints). The description does not disclose that this is a write operation requiring authentication, potential side effects, or failure conditions (e.g., missing linked resource).

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?

A single, front-loaded sentence efficiently conveys the core purpose. However, it could be slightly more structured with explicit parameter groupings.

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?

Despite having an output schema, the description lacks context about which parameters are typically required, the meaning of priority values, and how to interpret the return value. It is too brief for a creation tool with 10 optional parameters.

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%, so the baseline is 3. The description adds minimal extra meaning beyond the schema, only implying that at least one of issueId or projectId might be needed.

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 action (create) and resource (customer need) and specifies the linkage to an issue or project, distinguishing it from sibling tools like get, delete, or update customer needs.

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 vs alternatives like createCustomerNeedFromAttachment, nor any prerequisites or exclusions. The description only states the basic action.

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