Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

objectives-get-by-id

Retrieve a specific Shortcut objective using its public ID to access project management data, with options for full or slim field returns.

Instructions

Get a Shortcut objective by public ID

Input Schema

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

Implementation Reference

  • The handler function 'getObjective' that fetches the Shortcut objective (milestone) by public ID using the client, handles errors, and formats the result using inherited methods.
    async getObjective(objectivePublicId: number, full = false) {
    	const objective = await this.client.getMilestone(objectivePublicId);
    
    	if (!objective)
    		throw new Error(`Failed to retrieve Shortcut objective with public ID: ${objectivePublicId}`);
    
    	return this.toResult(
    		`Objective: ${objectivePublicId}`,
    		await this.entityWithRelatedEntities(objective, "objective", full),
    	);
    }
  • Input schema using Zod for the tool parameters: objectivePublicId (required positive number) and full (optional boolean, default false).
    {
    	objectivePublicId: z.number().positive().describe("The public ID of the objective to get"),
    	full: z
    		.boolean()
    		.optional()
    		.default(false)
    		.describe(
    			"True to return all objective fields from the API. False to return a slim version that excludes uncommon fields",
    		),
    },
  • Registration of the 'objectives-get-by-id' tool via server.addToolWithReadAccess, specifying name, description, input schema, and delegating to the getObjective handler.
    server.addToolWithReadAccess(
    	"objectives-get-by-id",
    	"Get a Shortcut objective by public ID",
    	{
    		objectivePublicId: z.number().positive().describe("The public ID of the objective to get"),
    		full: z
    			.boolean()
    			.optional()
    			.default(false)
    			.describe(
    				"True to return all objective fields from the API. False to return a slim version that excludes uncommon fields",
    			),
    	},
    	async ({ objectivePublicId, full }) => await tools.getObjective(objectivePublicId, full),
    );
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 mentions retrieving an objective but doesn't describe what happens if the ID doesn't exist, whether authentication is required, rate limits, or what the return format looks like. This is a significant gap for a read operation tool.

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 communicates the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool and gets straight to the point.

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?

For a retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what data is returned, error conditions, authentication requirements, or how this differs from the search tool. Given the lack of structured metadata, the description should provide more operational 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%, so the schema already fully documents both parameters. The description doesn't add any additional meaning about the parameters beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 objective by public ID'), making the purpose immediately understandable. However, it doesn't distinguish this tool from similar sibling tools like 'epics-get-by-id' or 'stories-get-by-id' beyond specifying it's for objectives rather than epics or stories.

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?

No guidance is provided about when to use this tool versus alternatives like 'objectives-search' or other get-by-id tools for different resource types. The description only states what it does, not when it's appropriate or what prerequisites might exist.

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