Shortcut MCP Server

Create Story Comment

create_story_comment

Add comments to Shortcut stories to provide feedback or updates. Post a comment directly to a story using its ID and text.

Instructions

Create a comment on a Shortcut story.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "story_id": "<story_id>",
      "text": "<text>"
    },
    "name": "create_story_comment"
  }
}

Input Schema

Name	Required	Description
`text`	Yes
`confirm`	No	Must be CONFIRM_WRITE to execute
`dry_run`	No
`story_id`	Yes
`author_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.8/5.0

Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits, but it only says 'Create a comment.' It omits critical details such as the confirm parameter requirement, dry_run option, potential side effects, or reversibility. This is a significant transparency gap for a write operation.

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?

The description is a single, focused sentence with no wasted words. It is efficiently structured, though extremely brief, which is appropriate for the simple action described but leaves out necessary context.

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 five parameters, no output schema, and no annotations, the description is insufficiently complete. It does not mention the confirmation workflow, dry-run capability, or optional author_id, leaving users without enough context to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% (only confirm is described). The description adds no parameter-level detail beyond 'comment' and 'story.' It does not explain author_id, confirm, dry_run, or the relationship between story_id and text, failing to compensate for the low schema coverage.

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 explicitly states 'Create a comment on a Shortcut story,' using a specific verb and resource. It clearly distinguishes from sibling tools like update_story_comment and delete_story_comment.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when to prefer this over update_story_comment or list_story_comments, or any exclusions.

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

Deploy Server