Skip to main content
Glama

linear_createComment

Post comments on Linear issues, projects, initiatives, updates, documents, or reply to existing comments using Markdown.

Instructions

Add a comment to an issue, project, initiative, update, document content, or as a threaded reply

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesText of the comment (Markdown supported)
postIdNoID of the post to comment on
issueIdNoID or identifier of the issue to comment on (e.g., ABC-123)
parentIdNoID of the parent comment to reply to (for threaded comments)
projectIdNoID of the project to comment on
quotedTextNoOptional quoted text for inline comments
initiativeIdNoID of the initiative to comment on
subscriberIdsNoOptional user IDs to subscribe to the comment target
projectUpdateIdNoID of the project update to comment on
documentContentIdNoID of the document content to anchor an inline comment to
initiativeUpdateIdNoID of the initiative update to comment on

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
bodyNo
userNo
issueNo
projectNo
parentIdNo
createdAtNo
updatedAtNo
initiativeNo
projectUpdateNo
initiativeUpdateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.3

TDQS

B3.4/5.0
Behavior2/5

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

Annotations are all false and provide no safety profile, so the description carries the burden of behavioral disclosure. It only states that a comment is added and does not mention side effects such as subscriber notifications, permission requirements, or non-idempotency.

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, front-loaded sentence with no filler. It efficiently communicates the action and the set of valid target resources.

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?

The tool has 11 parameters and multiple possible target IDs, but the description does not explain that at least one target must be supplied or how parentId relates to the other targets. This is a significant gap for correct invocation, despite the schema's per-parameter descriptions.

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 schema already documents each parameter, including Markdown support and target IDs. The description's list of targets roughly mirrors the schema but adds no new semantic detail about parameter relationships or constraints.

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 a specific verb ('Add a comment') and enumerates the full range of target resources: issue, project, initiative, update, document content, and threaded reply. This clearly distinguishes it from sibling comment tools like linear_updateComment and linear_deleteComment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool by naming the action and target types, but it does not explicitly state when not to use it or point to alternatives. There is no mention of linear_updateComment or linear_deleteComment for edit/delete scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools