Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

documents-list

List all documents in Shortcut project management to access and organize project files directly from AI tools.

Instructions

List all documents in Shortcut.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'documents-list' tool. Fetches all documents using this.client.listDocs() and returns a formatted list or error message using toResult.
    private async listDocuments() {
    	try {
    		const docs = await this.client.listDocs();
    		if (!docs?.length) return this.toResult("No documents were found.");
    		return this.toResult(`Found ${docs.length} documents.`, docs);
    	} catch (error) {
    		const errorMessage = error instanceof Error ? error.message : "Unknown error";
    		return this.toResult(`Failed to list documents: ${errorMessage}`);
    	}
    }
  • Registration of the 'documents-list' tool on the CustomMcpServer instance with read access and no parameters, linking to the listDocuments handler.
    server.addToolWithReadAccess(
    	"documents-list",
    	"List all documents in Shortcut.",
    	async () => await tools.listDocuments(),
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the action ('List all documents') without mentioning any behavioral traits like pagination, rate limits, permissions required, or what 'all documents' means in practice (e.g., workspace scope, archived items). This leaves significant gaps for a tool that presumably returns potentially large datasets.

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, efficient sentence that states the core purpose without any unnecessary words. It's appropriately sized for a simple list operation and front-loads the essential information.

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 the tool has no annotations, no output schema, and zero parameters, the description is incomplete. For a list operation that likely returns multiple documents, the description should address behavioral aspects like pagination, sorting, or scope limitations. The current description leaves too many operational questions unanswered.

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

Parameters4/5

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

The tool has zero parameters with 100% schema description coverage, so the schema already fully documents the absence of parameters. The description doesn't need to add parameter semantics, and it correctly doesn't mention any parameters. A baseline of 4 is appropriate since there are no parameters to explain.

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 clearly states the action ('List all documents') and the resource ('in Shortcut'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from its sibling 'documents-search', which could be used for similar listing purposes with filtering capabilities.

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 like 'documents-search' or 'documents-get-by-id'. There's no mention of use cases, prerequisites, or exclusions, leaving the agent to infer usage context from the tool name alone.

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