Skip to main content
Glama

Refresh all feeds

refresh_all_feeds
Idempotent

Refresh every saved RSS/Atom feed in one pass, collecting per-feed successes and failures so you can identify which subscriptions need attention.

Instructions

Refresh every saved feed, collecting per-feed successes and failures.

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_all_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
failedNoFeeds that failed
resultsNo
refreshedNoFeeds refreshed successfully (incl. 304)
new_entriesNoTotal new entries across all feeds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already disclose that this is a non-read-only, open-world, idempotent, non-destructive operation. The description adds that it collects per-feed successes and failures, which is useful behavioral context, but it does not discuss authentication, rate limits, or side effects beyond the aggregate result.

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?

The description is a single front-loaded sentence with no unnecessary wording. It states the action and the result behavior efficiently.

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?

Given that annotations cover safety and idempotency and an output schema exists, the description is nearly complete. It explains the broad scope and result aggregation, though it could mention prerequisites such as existing saved feeds or authentication needs.

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?

The tool takes zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and the empty input schema is consistent with a no-argument bulk refresh.

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?

The description states a specific verb and resource: 'Refresh every saved feed.' The scope word 'every' implies a bulk operation distinct from a single-feed refresh, but it does not explicitly name or contrast with the sibling tool refresh_feed.

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?

Usage is only implied by the phrase 'every saved feed.' There is no explicit guidance on when to use this bulk refresh instead of refresh_feed, nor any stated exclusions or prerequisites.

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