Skip to main content
Glama
Sign In
Shortcut MCP Server

Shortcut MCP Server

by ptamb3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Add Label to Epic

add_epic_label

Add labels to a Shortcut epic by specifying the full set of label IDs.

Instructions

Add a label to a Shortcut epic by providing the full set of label IDs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "epic_id": "<epic_id>",
      "label_ids": "<label_ids>"
    },
    "name": "add_epic_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be CONFIRM_WRITE to execute
dry_runNo
epic_idYes
label_idsYesFull list of label IDs for the epic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries full behavioral burden. It discloses the 'full set' behavior, indicating a replace operation, but fails to mention required confirmation ('confirm' parameter), dry-run behavior, permissions, reversibility, or side effects.

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, front-loaded sentence with no redundant words. Every word contributes to the core message, making it highly concise.

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 mutating tool with four parameters, no annotations, and no output schema, this description is incomplete. It omits crucial details about the confirm safety gate, dry-run behavior, and does not explain the destructive nature of replacing the full label set.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, and the description adds little beyond what is in the schema. It reinforces 'full list' for label_ids but provides no explanation for epic_id, confirm, or dry_run, leaving half the parameters undocumented.

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

Purpose5/5

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

The description clearly states the action ('Add a label') and the target resource ('Shortcut epic'), and specifies the method ('by providing the full set of label IDs'). This distinguishes it from sibling tools like 'add_story_label' and 'update_epic'.

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

Usage Guidelines3/5

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

The description implies usage context: to set the label set on an epic, you provide the full list of label IDs. However, it does not explicitly state when to use this tool versus alternatives like 'update_epic' or 'add_story_label', nor does it provide any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools