Skip to main content
Glama

Delete Stream

delete_stream
DestructiveIdempotent

[Act · writes · destructive] Delete a stream and its stream_runs. Posts collected by the stream stay in your library (stream_id is set to NULL via ON DELETE SET NULL) so historical data isn't lost. Auto-collection is deleted with the stream. own_profile streams cannot be deleted through this tool; the own profile is managed from Settings and billing.

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_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
stream_idYesStream ID from list_streams

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description goes well beyond them: it names exactly what is destroyed (stream_runs, auto-collection), what is preserved (posts remain, stream_id set to NULL via ON DELETE SET NULL), and which objects are out of scope. That is precisely the cascade semantics an agent needs before committing a destructive call.

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?

Three sentences, each doing distinct work: identity/action tag, data-retention consequences, and the eligibility restriction. The most consequential fact (posts are not lost) is front-loaded right after the action statement, with zero filler.

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?

For a single-parameter destructive mutation with no output schema, the description covers the important unknowns: cascade behavior, data retention, and blocked object types. It does not state what the call returns or how it behaves when the stream_id is unknown or already deleted, which is a minor remaining gap given idempotentHint.

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?

There is one parameter at 100% schema description coverage ('Stream ID from list_streams'), so the schema already carries the burden and baseline 3 applies. The description adds no format, validation, or sourcing detail for stream_id beyond the own_profile stream-type constraint.

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 stream and its stream_runs') plus the tag prefix '[Act · writes · destructive]', so the agent immediately knows this is an irreversible mutation on a named entity. The scope note distinguishes it from sibling mutations like pause_stream or resume_stream, which affect collection without removing the object.

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 exclusion: 'own_profile streams cannot be deleted through this tool; the own profile is managed from Settings and billing' — that is a real when-not-to-use rule. It stops short of naming the sibling a user should pick instead when they only want to stop collection (e.g., pause_stream), leaving that inference to the agent.

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