Skip to main content
Glama

Refresh feed

refresh_feed
Idempotent

Fetch a saved feed again by URL or feed ID, using ETag/Last-Modified headers to avoid re-downloading unchanged content.

Instructions

Fetch one saved feed again, using ETag/Last-Modified when the server sent them.

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": "refresh_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL of the feed to refresh
feed_idNoId of the feed to refresh

Output Schema

NameRequiredDescriptionDefault
okYes
feedNoState of the feed after the call
messageYesHuman-readable summary of what happened
new_entriesNoEntries inserted by this call
discovered_fromNoHTML page the feed URL was auto-discovered on, if any
removed_entriesNoEntries deleted together with the feed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotent=true and destructive=false, so the safety profile is covered. The description adds genuine mechanism information — that conditional requests via ETag/Last-Modified are used when the server provided them — which explains why the call is idempotent and what network behavior to expect. It does not say what local state changes, which is a minor gap.

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?

A single tight sentence with the action and the mechanism front-loaded; every clause carries information and nothing is repeated from the schema or 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 an output schema, full parameter documentation, and annotations covering the safety profile, the description only needs to convey action and mechanism, which it does. The remaining shortfall is that it never clarifies the url/feed_id selection rule or what the refresh does to stored entries.

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 coverage is 100%, so both parameters are already documented and the baseline of 3 applies. The description adds nothing about the relationship between url and feed_id, notably that both are optional and presumably mutually exclusive, which is the one semantic detail an agent would need.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Fetch one saved feed again" gives a concrete verb plus a scoped resource, and the word "one" implicitly separates it from refresh_all_feeds. It stops short of naming the sibling, but the scope is unmistakable.

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

Usage Guidelines3/5

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

The phrase "again" implies this is for re-fetching an already-saved feed, so usage is inferable, but there is no explicit when-to-use statement, no mention of when to prefer refresh_all_feeds, and no note about supplying url versus feed_id.

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