Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

stories-search

Search Shortcut stories using filters by name, description, owner, state, type, date range, and more. Retrieve specific stories or lists matching criteria to manage project tasks effectively.

Instructions

Find Shortcut stories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextPageTokenNoPagination token from previous search
idNoStory ID
nameNoName contains
descriptionNoDescription contains
commentNoComment contains
typeNoStory type
estimateNoPoint estimate
branchNoBranch name
commitNoCommit SHA
prNoPR number
projectNoProject ID
epicNoEpic ID
objectiveNoObjective ID
stateNoWorkflow state name
labelNoLabel name
ownerNoFilter by owner (use mention name or "me")
requesterNoFilter by requester (use mention name or "me")
teamNoTeam name or mention
skillSetNoSkill set
productAreaNoProduct area
technicalAreaNoTechnical area
priorityNoPriority level
severityNoSeverity level
isDoneNoFilter by completed status
isStartedNoFilter by started status
isUnstartedNoFilter by unstarted status
isUnestimatedNoFilter by unestimated status
isOverdueNoFilter by overdue status
isArchivedNoFilter by archived status
isBlockerNoFilter by blocking status
isBlockedNoFilter by blocked status
hasCommentNoFilter by presence of comment
hasLabelNoFilter by presence of label
hasDeadlineNoFilter by presence of deadline
hasOwnerNoFilter by presence of owner
hasPrNoFilter by presence of PR
hasCommitNoFilter by presence of commit
hasBranchNoFilter by presence of branch
hasEpicNoFilter by presence of epic
hasTaskNoFilter by presence of task
hasAttachmentNoFilter by presence of attachment
createdNoDate 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)
completedNoDate filter: "YYYY-MM-DD", "today", "yesterday", "tomorrow", or range "YYYY-MM-DD..YYYY-MM-DD" (use * for open bounds)
dueNoDate filter: "YYYY-MM-DD", "today", "yesterday", "tomorrow", or range "YYYY-MM-DD..YYYY-MM-DD" (use * for open bounds)
Behavior2/5

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

No annotations provided. Description fails to disclose search behavior (e.g., exact vs fuzzy matching, filter combinational logic, pagination). The only hint is the nextPageToken parameter, but not explained.

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

Conciseness3/5

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

Extremely concise (three words) but at the cost of missing essential information. Front-loaded, but insufficient for a complex tool.

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 45 parameters, no output schema, and many sibling tools, the description is inadequate. Does not explain search behavior, default sort, or how filters combine.

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 coverage is 100%, so each parameter already has a description. The tool description adds no additional meaning beyond what the schema provides.

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?

Description states verb 'Find' and resource 'Shortcut stories' clearly, distinguishing from other story operations like create or update. However, it does not differentiate from other search tools like epics-search or iterations-search.

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 guidance on when to use this tool vs alternatives such as stories-get-by-id, stories-create, or other search tools. Missing context for scenario-based selection.

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