Skip to main content
Glama
Sign In

Lion Reader

by com.lionreader
OverviewDiscussionsAdmin

create_collection

Idempotent

Create a collection: a named list of articles the user fills by hand (with add_to_collection), shown and tagged like a feed. For grouping whole feeds, use a tag (create_tag) instead. Returns it as a subscription; its id is the collectionId for the collection tools and the subscriptionId for list_entries and set_subscription_tags. If a collection with that name (ignoring case) already exists, returns it unchanged with created: false. Fails if the user is at their plan's subscription limit.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCollection name (unique per user ignoring case)

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 cover readOnly/idempotent/destructive/openWorld, but the description adds genuinely new behavior: duplicate-name requests return the existing collection with created: false, the returned object is a subscription whose id serves two different downstream roles, and failure occurs at the plan subscription limit. That is exactly the context annotations cannot express.

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?

Front-loads the definition, then routing, then return semantics, then failure mode — each sentence carries either disambiguation or behavioral payload. No filler, and the dense ID-mapping clause is justified because no output schema exists.

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?

With a single required parameter and no output schema, the description carries the return shape itself (subscription object, created flag, id dual-usage) plus the idempotency and limit behaviors. Nothing an agent needs to call it correctly and interpret the result 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% and already documents case-insensitive per-user uniqueness, so the description mostly reinforces it. It does add consequence-level meaning the schema cannot — that a name collision is not an error but an unchanged-return — which helps the agent interpret the single parameter's effect.

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+resource and immediately defines what a collection is (a hand-filled named list of articles), then distinguishes it from the sibling create_tag for the feed-grouping case. An agent can pick between the two without opening either 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 names the alternative (create_tag) and the condition that selects it, points to add_to_collection as the population mechanism, and warns of the plan subscription limit failure. When-to-use and when-not-to-use are both covered.

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