Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

add-external-link-to-story

Attach external URLs to Shortcut stories to connect project tasks with relevant web resources, documentation, or references.

Instructions

Add an external link to a Shortcut story

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storyPublicIdYesThe public ID of the story
externalLinkYesThe external link URL to add

Implementation Reference

  • The handler function that executes the tool: validates inputs, calls the Shortcut client to add the external link, and returns a formatted result message.
    async addExternalLinkToStory(storyPublicId: number, externalLink: string) {
    	if (!storyPublicId) throw new Error("Story public ID is required");
    	if (!externalLink) throw new Error("External link is required");
    
    	const updatedStory = await this.client.addExternalLinkToStory(storyPublicId, externalLink);
    
    	return this.toResult(
    		`Added external link to story sc-${storyPublicId}. Story URL: ${updatedStory.app_url}`,
    	);
    }
  • Registers the MCP tool 'add-external-link-to-story' with the server, providing name, description, input schema, and handler reference.
    server.tool(
    	"add-external-link-to-story",
    	"Add an external link to a Shortcut story",
    	{
    		storyPublicId: z.number().positive().describe("The public ID of the story"),
    		externalLink: z.string().url().max(2048).describe("The external link URL to add"),
    	},
    	async ({ storyPublicId, externalLink }) =>
    		await tools.addExternalLinkToStory(storyPublicId, externalLink),
    );
  • Zod schema defining the input parameters: storyPublicId (positive number) and externalLink (URL string).
    	storyPublicId: z.number().positive().describe("The public ID of the story"),
    	externalLink: z.string().url().max(2048).describe("The external link URL to add"),
    },
  • Inline handler in registration that delegates to the class method addExternalLinkToStory.
    	async ({ storyPublicId, externalLink }) =>
    		await tools.addExternalLinkToStory(storyPublicId, externalLink),
    );
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 the tool adds a link but doesn't clarify if this is a mutation (implied by 'Add'), what permissions are required, whether it's idempotent, or how it handles errors (e.g., invalid story ID or duplicate links). For a mutation tool with zero 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, efficient sentence that front-loads the core purpose without unnecessary words. It earns its place by clearly stating the tool's function, making it easy for an agent to parse quickly. No fluff or redundancy is present.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like side effects, error handling, or return values, which are critical for safe invocation. The high schema coverage helps with inputs, but overall context for usage and outcomes is lacking.

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%, with clear descriptions for both parameters (storyPublicId and externalLink), so the schema does the heavy lifting. The description adds no additional meaning beyond what's in the schema, such as format examples or constraints like URL validation. Baseline 3 is appropriate when the schema fully documents parameters.

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 ('Add') and the resource ('external link to a Shortcut story'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'remove-external-link-from-story' and 'set-story-external-links' by focusing on a single addition operation. However, it doesn't specify if this adds to existing links or replaces them, which slightly limits differentiation.

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 'set-story-external-links' or 'remove-external-link-from-story'. It lacks context about prerequisites (e.g., story existence, permissions) or exclusions, leaving the agent to infer usage from tool names alone without explicit 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/ampcome-mcps/shortcut-mcp'

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