Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

stories-add-external-link

Add external URLs to Shortcut stories to link related resources, documentation, or references directly within project management tasks.

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

  • Handler function that validates inputs, calls the Shortcut client to add the external link to the story, and returns a success message with the story URL.
    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 tool 'stories-add-external-link' with MCP server, including input schema validation using Zod and references the handler method.
    server.addToolWithWriteAccess(
    	"stories-add-external-link",
    	"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 input parameters: storyPublicId (positive number) and externalLink (valid URL up to 2048 chars).
    {
    	storyPublicId: z.number().positive().describe("The public ID of the story"),
    	externalLink: z.string().url().max(2048).describe("The external link URL to add"),
    },
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 action ('Add') but doesn't describe what happens on success (e.g., does it return the updated story?), error conditions (e.g., invalid URL, permission issues), or side effects (e.g., whether it triggers notifications). 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 directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, and there's no redundancy or fluff.

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 that this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like success/error responses, permissions, or side effects, which are critical for an agent to use it correctly. The schema handles parameters well, but the overall context for safe and effective use 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 both parameters clearly documented in the schema: 'storyPublicId' as a positive number and 'externalLink' as a URI up to 2048 characters. The description doesn't add any meaning beyond this (e.g., explaining what a 'public ID' is or URL format constraints), so it meets the baseline of 3 where the schema does the heavy lifting.

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 resource ('external link to a Shortcut story'), making the purpose immediately understandable. It distinguishes from siblings like 'stories-set-external-links' (which likely replaces all links) and 'stories-remove-external-link' by specifying addition rather than replacement or removal. However, it doesn't explicitly contrast with these alternatives in the text itself.

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 'stories-set-external-links' or 'stories-remove-external-link'. It doesn't mention prerequisites (e.g., needing story access), typical use cases, or constraints. The agent must infer usage from the name and context alone.

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