Skip to main content
Glama
Sign In
Shortcut MCP Server

Shortcut MCP Server

Official
by useshortcut
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Iterations: Get By ID

iterations-get-by-id
Read-onlyIdempotent

Retrieve a Shortcut iteration by its public ID. Optionally return all fields.

Instructions

Get a Shortcut iteration by public 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": {
      "iterationPublicId": "<iterationPublicId>"
    },
    "name": "iterations-get-by-id"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoReturn all fields (default: slim)
iterationPublicIdYesIteration ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.1
    • changedInput schema / properties / full / description
      Previous value: -"True to return all iteration fields from the API. False to return a slim version that excludes uncommon fields"New value: +"Return all fields (default: slim)"
    • changedInput schema / properties / iterationPublicId / description
      Previous value: -"The public ID of the iteration to get"New value: +"Iteration ID"
  2. Addedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, providing clear behavioral expectations. The description adds no new behavioral context beyond stating it gets by ID, which is consistent with annotations. No contradiction present.

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 sentence that efficiently communicates the tool's purpose with no extraneous words. It is appropriately sized for a simple retrieval tool.

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?

For a straightforward get-by-id tool with full schema coverage and informative annotations, the description is complete enough. It lacks details on output format or error behavior, but the simplicity of the tool and presence of sibling differentiation somewhat mitigate this.

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?

The schema already describes both parameters fully (iterationPublicId as required number, full as boolean with default). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate given 100% 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 clearly states the action ('Get'), the resource ('a Shortcut iteration'), and the identifier method ('by public ID'). It distinguishes itself from sibling tools like 'iterations-search' which retrieve by criteria, and 'iterations-get-stories' which retrieve associated stories.

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 explicit guidance on when to use this tool versus alternatives such as 'iterations-search', 'iterations-get-active', or 'iterations-get-upcoming'. The description implies use when the public ID is known, but does not provide exclusions 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