Skip to main content
Glama

Delete a BitFeed feed

delete_feed
Destructive

Permanently delete a feed.

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": {
      "bitfeed_token": "<bitfeed_token>",
      "feed_id": "<feed_id>"
    },
    "name": "delete_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
feed_idYes
bitfeed_tokenYesBitFeed account token (btf_…). Also accepted as Authorization: Bearer. Omit on the first create_feed to open an account; the token is returned once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds one piece of context beyond that: the deletion is permanent/irreversible. It says nothing about what happens to feed data, history, or whether confirmation is required.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity borders on under-specification for a destructive operation.

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 permanent, destructive tool with no output schema and an undocumented feed_id, the description should say more about consequences and prerequisites. As written, an agent knows only that deletion is permanent.

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 coverage is only 50%: bitfeed_token is documented in the schema, but feed_id has no description anywhere. The description adds no meaning about either parameter, so it fails to compensate for the gap.

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?

"Permanently delete a feed" states a specific verb and resource, and the word "permanently" separates it from reversible siblings like pause_feed. It does not explicitly name those siblings, so it stops short of a 5.

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 word "permanently" implies caution and that pause_feed/resume_feed are the non-destructive alternatives, but the description never says when to use this versus those. Usage is only implied.

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