Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

search-objectives

Search and filter Shortcut objectives by ID, name, description, state, owner, team, or date criteria to find specific project goals.

Instructions

Find Shortcut objectives.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoFind objectives matching the specified id
nameNoFind objectives matching the specified name
descriptionNoFind objectives matching the specified description
stateNoFind objectives matching the specified state
ownerNoFind entities where the owner match the specified user. This must either be the user's mention name or the keyword "me" for the current user.
requesterNoFind entities where the requester match the specified user. This must either be the user's mention name or the keyword "me" for the current user.
teamNoFind objectives matching the specified team. Should be a team mention name.
isUnstartedNoFind only entities that are unstarted when true, or only entities that are not unstarted when false.
isStartedNoFind only entities that are started when true, or only entities that are not started when false.
isDoneNoFind only entities that are completed when true, or only entities that are not completed when false.
isArchivedNoFind only entities that are archived when true, or only entities that are not archived when false.
hasOwnerNoFind only entities that have an owner when true, or only entities that do not have an owner when false. Example: hasOwner: true will find stories with an owner, hasOwner: false will find stories without an owner.
createdNoThe date in "YYYY-MM-DD" format, or one of the keywords: "yesterday", "today", "tomorrow", or a date range in the format "YYYY-MM-DD..YYYY-MM-DD". The date range can also be open ended by using "*" for one of the bounds. Examples: "2023-01-01", "today", "2023-01-01..*" (from Jan 1, 2023 to any future date), "*.2023-01-31" (any date up to Jan 31, 2023), "today..*" (from today onwards), "*.yesterday" (any date up to yesterday). The keywords cannot be used to calculate relative dates (e.g. the following are not valid: "today-1" or "tomorrow+1").
updatedNoThe date in "YYYY-MM-DD" format, or one of the keywords: "yesterday", "today", "tomorrow", or a date range in the format "YYYY-MM-DD..YYYY-MM-DD". The date range can also be open ended by using "*" for one of the bounds. Examples: "2023-01-01", "today", "2023-01-01..*" (from Jan 1, 2023 to any future date), "*.2023-01-31" (any date up to Jan 31, 2023), "today..*" (from today onwards), "*.yesterday" (any date up to yesterday). The keywords cannot be used to calculate relative dates (e.g. the following are not valid: "today-1" or "tomorrow+1").
completedNoThe date in "YYYY-MM-DD" format, or one of the keywords: "yesterday", "today", "tomorrow", or a date range in the format "YYYY-MM-DD..YYYY-MM-DD". The date range can also be open ended by using "*" for one of the bounds. Examples: "2023-01-01", "today", "2023-01-01..*" (from Jan 1, 2023 to any future date), "*.2023-01-31" (any date up to Jan 31, 2023), "today..*" (from today onwards), "*.yesterday" (any date up to yesterday). The keywords cannot be used to calculate relative dates (e.g. the following are not valid: "today-1" or "tomorrow+1").

Implementation Reference

  • The main handler function for the 'search-objectives' tool. It builds a search query using buildSearchQuery, searches for milestones (objectives) via the Shortcut client, handles empty results, and formats the output using inherited methods.
    async searchObjectives(params: QueryParams) {
    	const currentUser = await this.client.getCurrentUser();
    	const query = await buildSearchQuery(params, currentUser);
    	const { milestones, total } = await this.client.searchMilestones(query);
    
    	if (!milestones)
    		throw new Error(`Failed to search for milestones matching your query: "${query}"`);
    	if (!milestones.length) return this.toResult(`Result: No milestones found.`);
    
    	return this.toResult(
    		`Result (first ${milestones.length} shown of ${total} total milestones found):`,
    		await this.entitiesWithRelatedEntities(milestones, "objectives"),
    	);
    }
  • Zod input schema defining parameters for searching objectives, including filters for id, name, description, state, owner, team, status flags, and dates.
    	id: z.number().optional().describe("Find objectives matching the specified id"),
    	name: z.string().optional().describe("Find objectives matching the specified name"),
    	description: z
    		.string()
    		.optional()
    		.describe("Find objectives matching the specified description"),
    	state: z
    		.enum(["unstarted", "started", "done"])
    		.optional()
    		.describe("Find objectives matching the specified state"),
    	owner: user("owner"),
    	requester: user("requester"),
    	team: z
    		.string()
    		.optional()
    		.describe("Find objectives matching the specified team. Should be a team mention name."),
    	isUnstarted: is("unstarted"),
    	isStarted: is("started"),
    	isDone: is("completed"),
    	isArchived: is("archived"),
    	hasOwner: has("an owner"),
    	created: date(),
    	updated: date(),
    	completed: date(),
    },
  • Registers the 'search-objectives' tool on the MCP server with description, input schema, and handler reference.
    server.tool(
    	"search-objectives",
    	"Find Shortcut objectives.",
    	{
    		id: z.number().optional().describe("Find objectives matching the specified id"),
    		name: z.string().optional().describe("Find objectives matching the specified name"),
    		description: z
    			.string()
    			.optional()
    			.describe("Find objectives matching the specified description"),
    		state: z
    			.enum(["unstarted", "started", "done"])
    			.optional()
    			.describe("Find objectives matching the specified state"),
    		owner: user("owner"),
    		requester: user("requester"),
    		team: z
    			.string()
    			.optional()
    			.describe("Find objectives matching the specified team. Should be a team mention name."),
    		isUnstarted: is("unstarted"),
    		isStarted: is("started"),
    		isDone: is("completed"),
    		isArchived: is("archived"),
    		hasOwner: has("an owner"),
    		created: date(),
    		updated: date(),
    		completed: date(),
    	},
    	async (params) => await tools.searchObjectives(params),
    );
  • src/server.ts:36-36 (registration)
    Invokes ObjectiveTools.create to register all objective-related tools, including 'search-objectives', on the main MCP server.
    ObjectiveTools.create(client, server);
Behavior1/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 but provides none. It doesn't indicate whether this is a read-only operation, what permissions might be required, whether results are paginated, what format results return, or any rate limits. The single sentence 'Find Shortcut objectives' reveals nothing about the tool's behavior beyond the obvious.

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 maximally concise with a single three-word sentence that gets straight to the point. There's zero wasted verbiage or unnecessary elaboration. While it's severely under-specified, it's perfectly structured for its minimal content.

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

Completeness1/5

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

For a search tool with 15 parameters, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what 'objectives' are in the Shortcut context, what fields are searchable, whether this is a simple or advanced search, what the return format looks like, or any behavioral characteristics. The description fails to provide the necessary context for an agent to use this tool effectively.

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?

The schema description coverage is 100%, so the schema already documents all 15 parameters thoroughly with detailed descriptions and examples. The description adds no parameter information whatsoever, not even mentioning that filtering parameters exist. However, with complete schema coverage, the baseline score of 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Find Shortcut objectives' is a tautology that essentially restates the tool name 'search-objectives'. It provides no specific verb beyond 'find' and doesn't distinguish this search tool from other search tools on the server like 'search-epics', 'search-iterations', or 'search-stories'. The purpose is vague about what kind of search this performs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance about when to use this tool versus alternatives. There are multiple search tools on the server (search-objectives, search-epics, search-iterations, search-stories), but the description doesn't help an agent understand when to search for objectives versus other entity types. No context about prerequisites or typical use cases is provided.

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