Lion Reader

delete_collection

DestructiveIdempotent

Delete a collection. Can't be undone. Its articles stay in their feeds and in Saved unless deleteSavedArticles is set. To take only some articles out, use remove_from_collection instead. Fails with a not-found error if the user has no such collection (e.g. already 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": {
      "collectionId": "<collectionId>"
    },
    "name": "delete_collection"
  }
}

Input Schema

Name	Required	Description	Default
`collectionId`	Yes	The collection's subscription ID
`deleteSavedArticles`	No	Also permanently delete the saved articles in this collection that are in no other collection. Off by default: the articles stay in Saved.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare destructiveHint and idempotentHint, but the description goes further: it discloses irreversibility, the default cascade behavior (articles stay in feeds and Saved), the opt-in destructive variant, and the not-found error path. These are the exact behavioral facts an agent needs before calling a destructive write tool.

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 short sentences, front-loaded with the destructive action and its irreversibility, then the alternative, then the error case. Nothing is redundant and no sentence could be dropped without losing information.

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 two-parameter destructive tool with full schema coverage, no output schema, and no nesting, the definition covers action, side effects, alternatives, and error behavior. Nothing an agent needs in order to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters thoroughly, including the default for deleteSavedArticles. The description reinforces the consequence ('articles stay in their feeds and in Saved unless deleteSavedArticles is set'), which adds causal meaning rather than just restating the flag.

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 collection') and immediately scopes it: irreversible, with defined side effects on articles. An agent can distinguish it from siblings like remove_from_collection or delete_saved_article 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 Guidelines5/5

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

Explicitly routes the agent to an alternative ('To take only some articles out, use remove_from_collection instead'), which is a clear when-not condition. It also documents the failure mode ('Fails with a not-found error if the user has no such collection'), so the agent knows what a stale ID looks like.

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

All Lion Reader tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.