Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

stories-create-comment

Add comments to Shortcut stories to document progress, provide feedback, or share updates with team members directly from AI development environments.

Instructions

Create a comment on a story

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storyPublicIdYesThe public ID of the story
textYesThe text of the comment

Implementation Reference

  • The handler function that implements the core logic of the 'stories-create-comment' tool. It validates inputs, fetches the story, creates the comment using the ShortcutClientWrapper, and returns a success message with the comment URL.
    async createStoryComment({ storyPublicId, text }: { storyPublicId: number; text: string }) {
    	if (!storyPublicId) throw new Error("Story public ID is required");
    	if (!text) throw new Error("Story comment text is required");
    
    	const story = await this.client.getStory(storyPublicId);
    	if (!story)
    		throw new Error(`Failed to retrieve Shortcut story with public ID: ${storyPublicId}`);
    
    	const storyComment = await this.client.createStoryComment(storyPublicId, { text });
    
    	return this.toResult(
    		`Created comment on story sc-${storyPublicId}. Comment URL: ${storyComment.app_url}.`,
    	);
    }
  • Zod schema defining the input parameters for the tool: storyPublicId (positive number) and text (non-empty string). Used in the tool registration for input validation.
    	storyPublicId: z.number().positive().describe("The public ID of the story"),
    	text: z.string().min(1).describe("The text of the comment"),
    },
  • Registers the 'stories-create-comment' tool on the CustomMcpServer using addToolWithWriteAccess, providing the tool name, description, input schema, and reference to the handler function.
    server.addToolWithWriteAccess(
    	"stories-create-comment",
    	"Create a comment on a story",
    	{
    		storyPublicId: z.number().positive().describe("The public ID of the story"),
    		text: z.string().min(1).describe("The text of the comment"),
    	},
    	async (params) => await tools.createStoryComment(params),
    );
  • src/server.ts:47-47 (registration)
    Top-level invocation of StoryTools.create which adds all story-related tools, including 'stories-create-comment', to the MCP server.
    StoryTools.create(client, server);
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the tool creates a comment, implying a write operation, but doesn't disclose permissions needed, rate limits, error conditions, or what happens on success (e.g., comment ID returned). This leaves significant gaps for a mutation 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 with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain behavioral aspects like authentication needs, side effects, or return values, leaving the agent with insufficient context to use the tool effectively beyond basic parameter input.

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. The description adds no additional meaning beyond the schema's details about 'storyPublicId' and 'text', so it meets the baseline for high schema coverage without compensating value.

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 ('Create a comment') and target resource ('on a story'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'stories-add-subtask' or 'stories-add-task' that also create story-related content, missing explicit distinction.

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 on when to use this tool versus alternatives. The description lacks context about prerequisites (e.g., needing an existing story), exclusions, or comparisons to similar tools like 'stories-add-subtask' for different comment types.

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