Skip to main content
Glama
idyll
by idyll

search-stories

Search Shortcut stories using operators like type:, state:, owner:, and label: to filter by owner, requestor, state, and creation date.

Instructions

Search for stories in Shortcut using powerful search operators

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch query with optional operators (e.g., 'SMS type:feature state:"In Development" owner:john label:urgent'). Supports operators like type:, state:, owner:, label:, has:attachment, is:blocked, etc.
owner_nameNoFilter by owner name (person assigned to the story). Will be converted to owner:mention_name in the query.
requestor_nameNoFilter by requestor name (person who requested the story). Will be converted to requester:mention_name in the query.
state_nameNoFilter by workflow state name (e.g., 'In Development', 'Ready for Review'). Will be converted to state:"name" in the query.
created_afterNoFilter by creation date (YYYY-MM-DD). Can use 'yesterday' or 'today'. Will be converted to created:date..* in the query.
created_beforeNoFilter by creation date (YYYY-MM-DD). Can use 'yesterday' or 'today'. Will be converted to created:*..date in the query.
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as pagination, result format, rate limits, or auth requirements. The description only says 'Search for stories', leaving agents unaware of important behavioral details beyond the input schema.

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 one short sentence, which is efficient. It front-loads the key information. However, it could be slightly expanded without becoming verbose.

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?

No output schema exists, yet the description does not explain return values. Given 6 optional parameters and the complexity of a search tool, the description lacks details on pagination, result format, or error handling. The agent is left without critical completeness.

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 baseline is 3. The description briefly mentions operators, but the schema already explains them thoroughly. The description adds minimal value beyond the schema.

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 'Search for stories in Shortcut using powerful search operators', specifying the verb (search), resource (stories), and tool (Shortcut). It differentiates from sibling tools like list-stories-by-state-name or get-story by implying full-text search with operators.

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 hints at usage via 'powerful search operators' but does not explicitly state when to use this tool versus alternatives like list-stories-by-state-name or list-stories-by-status. No exclusions or when-not advise provided.

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/idyll/shortcut-mcp'

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