Skip to main content
Glama

delete_live_stream

Destructive

Delete a live stream. Call this only when the user explicitly asks.

Status `live` returns `code: live_api_error` and the stream stays up.
Stop it, then delete. Do not retry the delete while it is live.
`waiting` and `created` delete and return `status: deleted`.

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>"
    },
    "name": "delete_live_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
stream_idYesLive stream id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the supplied annotations (destructiveHint=true, idempotentHint=false) by naming the actual failure mode: a `live` stream returns `code: live_api_error` and stays up. It also sections behavior by state (`waiting`/`created` return `status: deleted`) and explicitly warns against retrying while live — the retry caveat directly reinforces the non-idempotent hint with operational detail.

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 permission constraint is front-loaded, then state-dependent outcomes follow in short line-separated blocks with inline code formatting. Every line carries distinct operational information; nothing is redundant.

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 single-parameter tool, the definition covers the authorization gate, the state preconditions, the specific error code, and the success outcome. The output schema handles the return shape, and the description still flags the key codes an agent must react to.

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?

One parameter at 100% schema coverage, with the pattern and length bounds already documented. The description adds no additional meaning about stream_id (e.g. where to obtain it), so the baseline of 3 applies.

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 ('Delete a live stream') that unambiguously separates it from get_/start_/stop_/update_live_stream. The opening sentence alone lets an agent pick this tool without opening the 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?

'Call this only when the user explicitly asks' is a real when-to-use constraint, and the live-state precondition ('Stop it, then delete') supplies the alternative flow. A slight gap: it says 'Stop it' rather than naming the stop tool, leaving the agent to infer the sibling.

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.