Skip to main content
Glama
Sign In
Shortcut MCP Server

Shortcut MCP Server

by ptamb3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Story Tasks

list_story_tasks

Retrieve checklist tasks for a Shortcut story by providing its story ID to view and manage task details.

Instructions

List checklist tasks 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>"
    },
    "name": "list_story_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
story_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states the list action without revealing any behavioral details such as ordering, pagination, whether completed tasks are included, or any side effects. The presence of a dry_run parameter suggests additional behavior, but the description does not address it.

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, clear sentence that immediately front-loads the tool's purpose. It contains no filler or redundant information, making it appropriately concise.

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 the simple parameter set and lack of annotations and output schema, the description is incomplete. It does not explain the purpose of dry_run, nor does it mention what the return value looks like (e.g., list of task objects). The tool has enough complexity that a bit more context would be beneficial.

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?

The description gives indirect meaning to story_id via 'on a Shortcut story', but it does not explain the dry_run parameter at all. Since schema description coverage is 0%, the description should compensate, but it fails to clarify the key boolean parameter.

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 clearly states the tool's function: 'List checklist tasks on a Shortcut story.' It uses a specific verb ('List') and a specific resource ('checklist tasks on a Shortcut story'). This distinguishes it from sibling tools like list_story_comments or list_story_external_links.

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 the tool is used to retrieve checklist tasks for a story, but it offers no explicit guidance on when to use it over alternatives or any exclusions. For example, it does not mention that it should not be used for story comments or other related data.

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