Skip to main content
Glama

shortcut_get_story

Read-onlyIdempotent

Retrieve a single Shortcut story by ID and API token to fetch its details for workflow automation, review, or reporting.

Instructions

Get a single Shortcut story by id.

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": {
      "api_token": "<api_token>",
      "story_id": "<story_id>"
    },
    "name": "shortcut_get_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
story_idYesShortcut story id
api_tokenYesShortcut API token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing beyond that – no note about what a story record contains, whether deleted/archived stories are visible, or what happens on an invalid id.

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?

A single nine-word sentence with no filler and the key qualifier ("by id") front-loaded. Nothing could be removed without losing information.

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

Completeness4/5

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

This is a simple two-parameter read tool with full schema coverage and annotations covering safety, so little more is needed. The one gap is that the description never signals the relationship to the search sibling or what the returned story includes, but no output schema exists to carry that burden either.

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 both story_id and api_token are already documented in the schema. The description's "by id" merely restates the story_id parameter and adds no format, type, or constraint detail beyond it, so the baseline of 3 applies.

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 gives a specific verb and resource ("Get a single Shortcut story") plus the lookup key ("by id"), which is unambiguous. It does not, however, distinguish itself from the sibling shortcut_search_stories, leaving the agent to infer which one to call.

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?

There is no statement of when to use this versus shortcut_search_stories, nor any prerequisite noted (e.g., you must first have a story id from a search). The only hint is the phrase "by id", which implies but never states the condition that selects this tool.

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