FeedKeeper Cloud

Digest of recent articles grouped by feed

get_digest

Read-onlyIdempotent

Returns recent articles grouped by subscribed feed with short summaries (newest first). This is the fastest and most token-efficient way to scan what is new. Defaults to unread articles. Do NOT use this tool for pagination, full text, or deep filtering—use list_items for cursor pagination or get_new_items for unread filtering, and follow up with get_item for full article bodies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_digest"
  }
}

Input Schema

Name	Required	Description
`hours`	No	Only include articles published in the last N hours (e.g. 24)
`since`	No	Only articles published at or after this ISO date or date-time (overrides hours)
`feedId`	No	Optional feed ID to limit the digest to a single feed
`folderId`	No	Optional folder ID to limit the digest to feeds in that folder
`unreadOnly`	No	When true (default), includes only unread articles; set false to include read articles
`snippetChars`	No	Maximum character length of each article summary snippet (default: 200)
`maxItemsPerFeed`	No	Maximum number of articles to include per feed (default: 5)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it is 'the fastest and most token-efficient way to scan', returns newest-first grouped results, and defaults to unread.

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, all earning their place: purpose and efficiency claim front-loaded, default stated, then explicit negative guidance with alternatives. No redundancy or filler.

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 read-only digest tool with no output schema, the description conveys enough about return shape (grouped by feed, short summaries, newest first) and defaults for an agent to call it correctly and know when not to.

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?

Schema description coverage is 100%, so hours, since, feedId, folderId, unreadOnly, snippetChars, and maxItemsPerFeed are all documented in the schema itself. The description only reinforces the unread default, adding little semantic detail beyond structured fields, so baseline 3 applies.

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 names a specific verb and resource ('Returns recent articles grouped by subscribed feed with short summaries') plus ordering ('newest first'), which lets an agent distinguish it from list_items, get_new_items, and get_item 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 gives explicit exclusions ('Do NOT use this tool for pagination, full text, or deep filtering') and routes to named alternatives for each case (list_items for cursor pagination, get_new_items for unread filtering, get_item for full bodies), plus states the default unread behavior.

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

All FeedKeeper Cloud 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.

Resources

Need Help?