Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

workflows-get-by-id

Retrieve a specific workflow from Shortcut project management using its public ID. Returns either full workflow details or a slim version based on your needs.

Instructions

Get a Shortcut workflow by public ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowPublicIdYesThe public ID of the workflow to get
fullNoTrue to return all workflow fields from the API. False to return a slim version that excludes uncommon fields

Implementation Reference

  • Handler function that fetches the workflow by public ID using the Shortcut client, handles not found case, and formats the response with related entities.
    async getWorkflow(workflowPublicId: number, full = false) {
    	const workflow = await this.client.getWorkflow(workflowPublicId);
    
    	if (!workflow) return this.toResult(`Workflow with public ID: ${workflowPublicId} not found.`);
    
    	return this.toResult(
    		`Workflow: ${workflow.id}`,
    		await this.entityWithRelatedEntities(workflow, "workflow", full),
    	);
    }
  • Registers the 'workflows-get-by-id' tool on the CustomMcpServer with input schema and lambda handler delegating to getWorkflow method.
    server.addToolWithReadAccess(
    	"workflows-get-by-id",
    	"Get a Shortcut workflow by public ID",
    	{
    		workflowPublicId: z.number().positive().describe("The public ID of the workflow to get"),
    		full: z
    			.boolean()
    			.optional()
    			.default(false)
    			.describe(
    				"True to return all workflow fields from the API. False to return a slim version that excludes uncommon fields",
    			),
    	},
    	async ({ workflowPublicId, full }) => await tools.getWorkflow(workflowPublicId, full),
    );
  • Zod input schema defining parameters: workflowPublicId (required positive number) and full (optional boolean, default false).
    {
    	workflowPublicId: z.number().positive().describe("The public ID of the workflow to get"),
    	full: z
    		.boolean()
    		.optional()
    		.default(false)
    		.describe(
    			"True to return all workflow fields from the API. False to return a slim version that excludes uncommon fields",
    		),
    },
  • Calls helper method to enrich the workflow entity with related entities, used in the response formatting.
    	await this.entityWithRelatedEntities(workflow, "workflow", full),
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), but doesn't mention authentication requirements, rate limits, error handling, or what the response looks like (e.g., format, fields). For a tool with no annotation coverage, this is a significant gap in transparency.

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, front-loaded sentence that directly states the tool's purpose without unnecessary words. It efficiently communicates the core functionality, earning a top score for conciseness and structure.

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 no annotations and no output schema, the description is incomplete for a tool that retrieves data. It doesn't explain the return values, error conditions, or behavioral traits like authentication needs. For a read operation with 2 parameters, this leaves significant gaps in context.

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%, meaning the input schema fully documents both parameters ('workflowPublicId' and 'full'). The description adds no additional meaning beyond what the schema provides, such as examples or edge cases, so it meets the baseline of 3 without compensating for any gaps.

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 ('Get') and resource ('a Shortcut workflow by public ID'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'workflows-list' or 'workflows-get-default', which would require explicit comparison to achieve a score of 5.

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 'workflows-list' or 'workflows-get-default'. It lacks context about prerequisites, such as needing a specific workflow ID, or exclusions, leaving the agent without usage direction.

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