Skip to main content
Glama
Sign In
Shortcut MCP Server

Shortcut MCP Server

by ptamb3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Linked Files

list_linked_files

Find every linked file across your Shortcut workspace. This action returns all file attachments for stories, epics, and projects.

Instructions

List all linked files in your Shortcut workspace.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_linked_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits, but it only states 'list all' without indicating read-only status, pagination, or any side effects. The presence of a dry_run parameter is unexplained, introducing uncertainty about whether the operation could have side effects.

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, focused sentence with no redundant words. It is front-loaded with the action and resource, making it appropriately concise for a simple list operation.

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?

While the tool is simple, the description is incomplete: it fails to explain linked files, the purpose of dry_run, or any filtering/pagination behavior. The lack of an output schema does not excuse the missing parameter context, and the description provides minimal assistance for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter 'dry_run' has no schema description (0% coverage), and the description does not explain its meaning or behavior. The description adds no value beyond the schema's bare type declaration, leaving the agent completely uninformed about how to use the 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 uses a specific verb 'list' with resource 'linked files' and scope 'all in your Shortcut workspace', making it clear what resource is being acted on. It is easily distinguishable from sibling list tools that target other resources like projects, members, or milestones.

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?

There is no guidance on when to use this tool versus alternatives such as get_linked_file for a single file or create_linked_file for adding a linked file. The description does not mention any prerequisites or exclusions, leaving the agent with no direction on tool selection.

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