Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

stories-remove-subtask

Convert a sub-task into a standalone story by removing its parent relationship in Shortcut project management.

Instructions

Remove a story from its parent. The sub-task will become a regular story.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subTaskPublicIdYesThe public ID of the sub-task story

Implementation Reference

  • Handler function that fetches the subtask story and updates it by setting parent_story_id to null, effectively removing it from its parent.
    async removeSubTaskFromParent({ subTaskPublicId }: { subTaskPublicId: number }) {
    	if (!subTaskPublicId) throw new Error("ID of sub-task story is required");
    
    	const subTask = await this.client.getStory(subTaskPublicId);
    	if (!subTask) throw new Error(`Failed to retrieve story with public ID: ${subTaskPublicId}`);
    
    	await this.client.updateStory(subTaskPublicId, {
    		parent_story_id: null,
    	});
    
    	return this.toResult(`Removed story sc-${subTaskPublicId} from its parent story`);
    }
  • Zod schema defining the input parameter subTaskPublicId for the stories-remove-subtask tool.
    {
    	subTaskPublicId: z.number().positive().describe("The public ID of the sub-task story"),
    },
  • Registration of the stories-remove-subtask tool using server.addToolWithWriteAccess, linking to the handler and schema.
    server.addToolWithWriteAccess(
    	"stories-remove-subtask",
    	"Remove a story from its parent. The sub-task will become a regular story.",
    	{
    		subTaskPublicId: z.number().positive().describe("The public ID of the sub-task story"),
    	},
    	async (params) => await tools.removeSubTaskFromParent(params),
    );
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. It states the tool removes a story from its parent and converts it to a regular story, but lacks details on permissions required, whether the change is reversible, error handling (e.g., if the story isn't a sub-task), or rate limits. This is a significant gap 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 two concise sentences that are front-loaded with the core action and outcome. There is no wasted language, and it efficiently communicates the essential information without redundancy.

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 lacks behavioral details (e.g., side effects, error conditions) and doesn't explain the return value or what 'becoming a regular story' entails operationally. More context is needed given the tool's complexity.

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 the parameter 'subTaskPublicId' clearly documented in the schema. The description doesn't add any meaning beyond this, such as explaining what a 'public ID' entails or providing examples. Baseline 3 is appropriate when the schema handles parameter documentation adequately.

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 ('Remove a story from its parent') and the outcome ('The sub-task will become a regular story'), specifying both the verb and resource. However, it doesn't explicitly differentiate from sibling tools like 'stories-remove-external-link' or 'stories-unassign-current-user', which also involve removal operations on 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the story must be a sub-task), exclusions, or compare to related tools like 'stories-add-subtask' or 'stories-update-task' for context.

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