Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

list-workflows

View all available workflows in Shortcut to manage project processes and track progress across teams.

Instructions

List all Shortcut workflows

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that fetches all workflows using the Shortcut client and returns a formatted result or 'No workflows found' if none exist.
    async listWorkflows() {
    	const workflows = await this.client.getWorkflows();
    
    	if (!workflows.length) return this.toResult(`No workflows found.`);
    
    	return this.toResult(
    		`Result (first ${workflows.length} shown of ${workflows.length} total workflows found):`,
    		await this.entitiesWithRelatedEntities(workflows, "workflows"),
    	);
    }
  • MCP server tool registration for 'list-workflows', which calls the listWorkflows handler with no parameters.
    server.tool(
    	"list-workflows",
    	"List all Shortcut workflows",
    	async () => await tools.listWorkflows(),
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like whether this returns all workflows at once, if there's pagination, what permissions are needed, or the format of returned data. For a list operation with zero annotation coverage, this is insufficient.

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 with zero waste—'List all Shortcut workflows'—front-loading the key information. Every word earns its place, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'list all' entails (e.g., pagination, sorting, or data format), which is critical for a list tool. With no structured fields to compensate, the description should provide more behavioral context.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, focusing instead on the tool's purpose, which aligns with the schema's simplicity.

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 verb ('List') and resource ('Shortcut workflows'), making the purpose immediately understandable. It doesn't differentiate from siblings like 'get-workflow' or 'search-stories', but it's specific enough to avoid confusion with unrelated tools.

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 'get-workflow' (for a single workflow) or 'search-stories' (for filtered results). It simply states what it does without context about use cases or prerequisites.

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

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