Skip to main content
Glama

Withdraw board release

yank_board_release
DestructiveIdempotent

Withdraw a release by name (the tag argument) on a board you own. A withdrawn release keeps its page, which says when and why it was withdrawn and that nobody should build from it; it stops resolving as a version selector, is no longer the latest release, cannot be ordered, and no longer counts toward the board's 100 releases. Its name stays taken. This is a write that cannot be undone; it needs the same save authority as create_board_release. Withdraw only when the user has asked for this exact release to be withdrawn. The result reports the state as yanked.

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": {
      "board": "<board>",
      "tag": "<tag>",
      "reason": "<reason>"
    },
    "name": "yank_board_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYesThe name of the release to withdraw.
boardYesA board you can read: handle/slug or a boardrepo.com URL.
reasonYesWhy the release is withdrawn; shown on the release page.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare destructive/idempotent/openWorld; the description adds substantial context beyond them: the release page is retained with the reason, the name remains taken, it stops resolving as a version selector, cannot be ordered, and no longer counts toward the 100-release cap. It also discloses irreversibility and the permission requirement (same save authority as create_board_release), which is exactly the disclosure a destructive tool needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then consequences, then constraints, then return state — a sensible order with no filler sentences. The consequence clause is long and the final sentence ('The result reports the state as yanked') is somewhat redundant given an output schema exists, costing a little efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, irreversible write with an output schema and full schema coverage, the description covers irreversibility, permissions, post-state effects, naming constraints, and the calling condition. An agent has everything needed to invoke it correctly and safely.

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%, so the baseline is 3. The description adds only that 'tag' is the release name and that the board must be one the caller has save authority over — the latter slightly tensions with the schema's 'A board you can read', which could momentarily confuse an agent about the required permission level.

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?

States a specific verb and resource ('Withdraw a release by name (the tag argument) on a board you own') and ties the 'tag' terminology to the parameter the agent will actually see. It is clearly distinguishable from create_board_release and list_board_releases without opening any schema.

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

Usage Guidelines4/5

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

Gives an explicit gating condition: 'Withdraw only when the user has asked for this exact release to be withdrawn', which implies a when-not for speculative or bulk withdrawals. It does not name an alternative tool for discovering the correct tag, but the guidance is far stronger than typical.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources