Skip to main content
Glama
Sign In

Lion Reader

by com.lionreader
OverviewDiscussionsAdmin

delete_saved_article

DestructiveIdempotent

Permanently delete an article from the user's Saved list (saved by URL or uploaded), and from every collection. Can't be undone. Feed entries can't be deleted: mark them read, or take them out of a collection with remove_from_collection. Returns { deleted: false } if the ID isn't one of the user's saved articles (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": {
      "articleId": "<articleId>"
    },
    "name": "delete_saved_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
articleIdYesThe saved article ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/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, so the safety profile is known, but the description adds material context beyond them: the deletion cascades out of every collection, it is irreversible ('Can't be undone'), and the not-found path returns { deleted: false } rather than erroring. The 'already deleted' example also concretely explains what idempotency means here.

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 carrying distinct information: the action and scope, the irreversibility and the excluded case with alternatives, then the failure return. The destructive warning and scope are front-loaded, and there is no redundant restatement of the title.

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 single-parameter destructive tool with no output schema, the description covers everything an agent needs: scope, irreversibility, cascade behavior, excluded resource type with alternatives, and the not-found return shape. Nothing material is left to inference.

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% for the single articleId parameter, so the baseline would be 3. The description earns above baseline by clarifying which IDs are valid — saved-by-URL or uploaded articles — and by noting that an ID outside that set yields { deleted: false }, which meaningfully narrows interpretation of the parameter.

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?

The description opens with a specific verb and resource ('Permanently delete an article') and immediately bounds the scope to 'the user's Saved list (saved by URL or uploaded)' and 'every collection'. It explicitly carves out feed entries, which lets an agent distinguish this from siblings like mark_entries_read or remove_from_collection without opening a 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?

It states both when to use this tool and when not to, naming the two concrete alternatives for the excluded case: 'Feed entries can't be deleted: mark them read, or take them out of a collection with remove_from_collection.' That is an explicit routing rule, not an implied one.

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

All Lion Reader toolsInspect
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.

Resources