Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut
OverviewSchemaRelated ServersScoreDiscussions(1)
TypeScript
Remote

Iterations: Search

iterations-search
Read-onlyIdempotent

Search for Shortcut iterations by ID, name, description, state, team, or date range. Filter results with pagination support.

Instructions

Find Shortcut iterations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoIteration ID
nameNoName contains
teamNoTeam ID or mention name
stateNoIteration state
createdNoDate filter: "YYYY-MM-DD", "today", "yesterday", "tomorrow", or range "YYYY-MM-DD..YYYY-MM-DD" (use * for open bounds)
endDateNoDate filter: "YYYY-MM-DD", "today", "yesterday", "tomorrow", or range "YYYY-MM-DD..YYYY-MM-DD" (use * for open bounds)
updatedNoDate filter: "YYYY-MM-DD", "today", "yesterday", "tomorrow", or range "YYYY-MM-DD..YYYY-MM-DD" (use * for open bounds)
startDateNoDate filter: "YYYY-MM-DD", "today", "yesterday", "tomorrow", or range "YYYY-MM-DD..YYYY-MM-DD" (use * for open bounds)
descriptionNoDescription contains
nextPageTokenNoPagination token from previous search

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changedv0.15.1
    • changedInput schema / properties / created / description
      Previous value: -"The date in \"YYYY-MM-DD\" format, or one of the keywords: \"yesterday\", \"today\", \"tomorrow\", or a date range in the format \"YYYY-MM-DD..YYYY-MM-DD\". The date range can also be open ended by using \"*\" for one of the bounds. Examples: \"2023-01-01\", \"today\", \"2023-01-01..*\" (from Jan 1, 2023 to any future date), \"*.2023-01-31\" (any date up to Jan 31, 2023), \"today..*\" (from today onwards), \"*.yesterday\" (any date up to yesterday). The keywords cannot be used to calculate relative dates (e.g. the following are not valid: \"today-1\" or \"tomorrow+1\")."New value: +"Date filter: \"YYYY-MM-DD\", \"today\", \"yesterday\", \"tomorrow\", or range \"YYYY-MM-DD..YYYY-MM-DD\" (use * for open bounds)"
    • changedInput schema / properties / description / description
      Previous value: -"Find only iterations matching the specified description"New value: +"Description contains"
    • changedInput schema / properties / endDate / description
      Previous value: -"The date in \"YYYY-MM-DD\" format, or one of the keywords: \"yesterday\", \"today\", \"tomorrow\", or a date range in the format \"YYYY-MM-DD..YYYY-MM-DD\". The date range can also be open ended by using \"*\" for one of the bounds. Examples: \"2023-01-01\", \"today\", \"2023-01-01..*\" (from Jan 1, 2023 to any future date), \"*.2023-01-31\" (any date up to Jan 31, 2023), \"today..*\" (from today onwards), \"*.yesterday\" (any date up to yesterday). The keywords cannot be used to calculate relative dates (e.g. the following are not valid: \"today-1\" or \"tomorrow+1\")."New value: +"Date filter: \"YYYY-MM-DD\", \"today\", \"yesterday\", \"tomorrow\", or range \"YYYY-MM-DD..YYYY-MM-DD\" (use * for open bounds)"
    • changedInput schema / properties / id / description
      Previous value: -"Find only iterations with the specified public ID"New value: +"Iteration ID"
    • changedInput schema / properties / name / description
      Previous value: -"Find only iterations matching the specified name"New value: +"Name contains"
    • changedInput schema / properties / nextPageToken / description
      Previous value: -"If a next_page_token was returned from the search result, pass it in to get the next page of results. Should be combined with the original search parameters."New value: +"Pagination token from previous search"
    • changedInput schema / properties / startDate / description
      Previous value: -"The date in \"YYYY-MM-DD\" format, or one of the keywords: \"yesterday\", \"today\", \"tomorrow\", or a date range in the format \"YYYY-MM-DD..YYYY-MM-DD\". The date range can also be open ended by using \"*\" for one of the bounds. Examples: \"2023-01-01\", \"today\", \"2023-01-01..*\" (from Jan 1, 2023 to any future date), \"*.2023-01-31\" (any date up to Jan 31, 2023), \"today..*\" (from today onwards), \"*.yesterday\" (any date up to yesterday). The keywords cannot be used to calculate relative dates (e.g. the following are not valid: \"today-1\" or \"tomorrow+1\")."New value: +"Date filter: \"YYYY-MM-DD\", \"today\", \"yesterday\", \"tomorrow\", or range \"YYYY-MM-DD..YYYY-MM-DD\" (use * for open bounds)"
    • changedInput schema / properties / state / description
      Previous value: -"Find only iterations matching the specified state"New value: +"Iteration state"
    • changedInput schema / properties / team / description
      Previous value: -"Find only iterations matching the specified team. This can be a team ID or mention name."New value: +"Team ID or mention name"
    • changedInput schema / properties / updated / description
      Previous value: -"The date in \"YYYY-MM-DD\" format, or one of the keywords: \"yesterday\", \"today\", \"tomorrow\", or a date range in the format \"YYYY-MM-DD..YYYY-MM-DD\". The date range can also be open ended by using \"*\" for one of the bounds. Examples: \"2023-01-01\", \"today\", \"2023-01-01..*\" (from Jan 1, 2023 to any future date), \"*.2023-01-31\" (any date up to Jan 31, 2023), \"today..*\" (from today onwards), \"*.yesterday\" (any date up to yesterday). The keywords cannot be used to calculate relative dates (e.g. the following are not valid: \"today-1\" or \"tomorrow+1\")."New value: +"Date filter: \"YYYY-MM-DD\", \"today\", \"yesterday\", \"tomorrow\", or range \"YYYY-MM-DD..YYYY-MM-DD\" (use * for open bounds)"
  2. Addedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no behavioral context beyond the generic 'find' verb. It does not mention pagination, rate limits, or any potential side effects, which would be helpful for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at three words. While it is not verbose, it sacrifices clarity and completeness. It is front-loaded but lacks substance.

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?

The description is minimal and does not mention return values, pagination, or output format. Given the complexity of the input schema (10 optional parameters) and the lack of an output schema, the description is incomplete for an agent to fully understand the tool's behavior.

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%. Each parameter has a clear description in the schema. The tool description adds no extra semantic value beyond what the schema already provides, warranting a baseline score of 3.

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 'Find Shortcut iterations.' clearly states the tool's action (find) and resource (iterations). However, it does not differentiate from sibling iteration tools like iterations-get-active or iterations-get-upcoming, which have overlapping purposes.

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. It does not mention any prerequisites, exclusions, or context that would help an agent decide between this and sibling search/list tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/useshortcut/mcp-server-shortcut'

If you have feedback or need assistance with the MCP directory API, please join our Discord server