Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

workflows-list

Retrieve all available workflows from the Shortcut project management platform to view and manage project processes.

Instructions

List all Shortcut workflows

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function listWorkflows() that implements the core logic for the "workflows-list" tool. It retrieves all workflows from the Shortcut client, handles empty results, and formats the output using base tool methods.
    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"),
    	);
    }
  • Registration of the "workflows-list" tool using server.addToolWithReadAccess, specifying the tool name, description, and linking to the listWorkflows handler.
    server.addToolWithReadAccess(
    	"workflows-list",
    	"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 the full burden of behavioral disclosure. While 'List' suggests a read-only operation, it doesn't specify whether this requires authentication, how results are returned (e.g., pagination, sorting), rate limits, or what happens if no workflows exist. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 immediately conveys the core functionality without any wasted words. It's front-loaded with the essential action and resource, making it easy to parse. Every word earns its place in this minimal yet complete statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema), the description is adequate for basic understanding but incomplete for practical use. Without annotations or output schema, it doesn't address behavioral aspects like authentication requirements, result format, or error conditions. For a list operation that likely returns structured data, more context would be helpful despite the tool's straightforward nature.

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% description coverage, so the schema fully documents the lack of parameters. The description appropriately doesn't add parameter information beyond what's already covered, maintaining a baseline score of 4 for tools with no parameters. No additional semantic value is needed or provided.

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 ('all Shortcut workflows'), making the purpose immediately understandable. It distinguishes this from other workflow tools like 'workflows-get-by-id' and 'workflows-get-default' by indicating it returns all workflows rather than specific ones. However, it doesn't explicitly differentiate from other list tools like 'documents-list' or 'teams-list' beyond the resource type.

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 implies usage when needing to retrieve all workflows, but provides no explicit guidance on when to use this versus alternatives like 'workflows-get-by-id' for specific workflows or 'workflows-get-default' for the default workflow. There's no mention of prerequisites, limitations, or when not to use this tool, leaving usage context somewhat vague.

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