Skip to main content
Glama
Sign In
Shortcut MCP Server

Shortcut MCP Server

Official
by useshortcut
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Stories: Set External Links

stories-set-external-links

Replace all external links on a story with specified URLs. Provide story ID and array of new URLs to overwrite existing links.

Instructions

Replace all external links on a 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": {
      "storyPublicId": "<storyPublicId>",
      "externalLinks": "<externalLinks>"
    },
    "name": "stories-set-external-links"
  }
}

Input Schema

NameRequiredDescriptionDefault
externalLinksYesURLs to set (replaces all)
storyPublicIdYesStory ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.1
    • changedInput schema / properties / externalLinks / description
      Previous value: -"Array of external link URLs to set (replaces all existing links)"New value: +"URLs to set (replaces all)"
    • changedInput schema / properties / storyPublicId / description
      Previous value: -"The public ID of the story"New value: +"Story ID"
  2. Addedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds 'replace all,' which clarifies the mutation behavior. It does not contradict annotations and provides enough context about what the tool does, though it could mention reversibility or permissions.

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 7-word sentence that is both concise and front-loaded. Every word is informative with no unnecessary elaboration.

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

Completeness3/5

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

For a simple tool with 2 parameters and no output schema, the description covers the basic action but lacks contextual guidance such as when to use this tool over similar ones or what the result looks like. It is minimally adequate but could be more helpful.

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%, with both parameters having descriptions in the schema. The tool description does not add any new information about the parameters beyond what is already in the schema, such as format or usage notes.

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 the specific verb 'replace' with the resource 'external links' and the scope 'on a story'. It clearly distinguishes from sibling tools like 'stories-add-external-link' and 'stories-remove-external-link' by indicating a wholesale replacement rather than incremental changes.

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 vs. alternatives such as 'stories-add-external-link' or 'stories-remove-external-link'. It does not state that this tool should be used for setting all links at once, nor does it mention any prerequisites or context.

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