Skip to main content
Glama

remove_playback_id

Destructive

Remove a playback id. Call this only when the user asks.

Refused with `code: stream_active` while the stream is running, because
the live API would stop the broadcast.

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": {
      "stream_id": "<stream_id>",
      "playback_id": "<playback_id>"
    },
    "name": "remove_playback_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
stream_idYesLive stream id.
playback_idYesPlayback id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / playback_id / pattern
      Added value: +"^[A-Za-z0-9_-]{1,64}$"
    • addedInput schema / properties / stream_id / pattern
      Added value: +"^[A-Za-z0-9_-]{1,64}$"
  2. Added
  3. Removed
  4. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the danger profile is covered. The description adds genuine new information by disclosing the specific failure mode: a refusal with `code: stream_active` while the stream is live, and the reason (the live API would stop the broadcast). That is useful but narrow, and the description says nothing about reversibility or whether other playback ids are affected.

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?

Two compact sentences, with the action and the invocation guardrail front-loaded and the failure condition following. No filler or restated title.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and the description covers the destructive nature plus the one failure path that matters. It could do slightly more on confirmation expectations and post-refusal next steps for a non-idempotent destructive operation, but it is broadly complete.

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 coverage is 100% with both required parameters (stream_id, playback_id) fully described, so the schema carries the parameter burden. The description adds no syntax, format, or constraint detail beyond what the schema already states, which is exactly the baseline-3 case.

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 opens with a specific verb+resource pair, "Remove a playback id," which makes the mutation and its target unambiguous against siblings like add_playback_id. It stops short of naming a sibling to differentiate from, so it lands at clear-but-not-differentiating.

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?

"Call this only when the user asks" gives an explicit invocation guardrail that rules out proactive removal, and the stream-active refusal describes a real precondition an agent must anticipate. It does not name the counterpart tool (add_playback_id) or tell the agent what to do when the removal is refused, leaving a small gap.

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.