FeedKeeper Cloud

Get single article content and metadata

get_item

Read-onlyIdempotent

Returns full metadata and stored content (HTML or plain text) for a single subscribed article by its numeric itemId. Content is chunked at 40,000 characters; use offset and content.revision to paginate large articles. If an article only has an RSS teaser/summary and full web text is desired, call fetch_full_text.

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

Input Schema

Name	Required	Description
`format`	No	Format of content: 'html' for sanitized HTML, 'text' for plain text extraction
`itemId`	Yes	The numeric ID of the article to retrieve
`offset`	No	Character offset for reading subsequent chunks of large articles
`maxChars`	No	Maximum character length of content to return (up to 40,000)
`revision`	No	Revision token returned in previous chunk to ensure pagination consistency

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description adds genuinely new operational facts: content is chunked at 40,000 characters and pagination requires carrying the revision token forward for consistency. It also discloses the teaser-vs-full-text limitation, which the 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?

Three sentences, front-loaded with what is returned and the identifier needed, then pagination mechanics, then the fallback route. No filler or restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must characterize the return value; it does so at a high level (metadata plus HTML or plain text, chunked) but does not indicate which metadata fields come back. Adequate for a five-parameter read tool, with a small remaining gap.

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 baseline is 3; the description earns above that by explaining the offset + revision pairing as a pagination protocol rather than two independent integers. Minor issue: it refers to 'content.revision' where the parameter is named 'revision', which could momentarily confuse an agent.

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 uses a specific verb and resource: 'Returns full metadata and stored content (HTML or plain text) for a single subscribed article by its numeric itemId.' The scope 'single subscribed article' distinguishes it from the list/search siblings, which all operate on sets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives an explicit routing rule to fetch_full_text when only an RSS teaser is stored, and explains when to paginate via offset and revision. It does not contrast with list_items or search_items (e.g., that this is the follow-up call once an itemId is known), so the guidance is strong but not complete.

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?