Shortcut MCP Server

Create Story Link

create_story_link

Define relationships between stories by linking them as blocks, duplicates, or relates to.

Instructions

Link two stories together (e.g. blocks, is blocked by, relates to, duplicates).

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": {
      "subject_id": "<subject_id>",
      "object_id": "<object_id>",
      "verb": "<verb>"
    },
    "name": "create_story_link"
  }
}

Input Schema

Name	Required	Description
`verb`	Yes	Relationship: subject 'blocks' object, subject 'duplicates' object, etc.
`confirm`	No	Must be CONFIRM_WRITE to execute
`dry_run`	No
`object_id`	Yes	The story that is the object
`subject_id`	Yes	The story that is the subject

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it does not mention that this is a write operation, the confirm parameter, or the dry_run option. It also incorrectly suggests 'is blocked by' as a valid verb, potentially misleading agents. This falls short of expected transparency.

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 a single concise sentence, but it is underspecified. It lacks any structured breakdown of behavior or parameters. It is short but not optimally informative, making it only minimally acceptable.

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?

For a tool with 5 parameters, no annotations, and no output schema, this description is incomplete. It omits information about confirm and dry_run, does not explain the direction of the link, and fails to describe return values or error behavior, leaving significant gaps for an agent to invoke it 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?

Although the schema already documents 80% of parameters, the description adds little value. It does not clarify the directional semantics of subject_id and object_id beyond what the schema says, and the 'is blocked by' example is inconsistent with the verb enum, potentially causing incorrect parameter usage.

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?

The description clearly states the tool's purpose: linking two stories together with example relationship types. It is distinguishable from siblings like delete_story_link and create_story. However, it lists 'is blocked by' as an example although the schema enum does not include it, which slightly muddles the precise set of allowed verbs.

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?

The description provides no guidance on when to use this tool versus alternatives such as delete_story_link or update_story. It does not mention any specific scenarios, prerequisites, or exclusions, leaving the agent without usage context.

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

Deploy Server