Skip to main content
Glama

Update feed

update_feed
Idempotent

Rename a followed feed, change its address, or replace its categories. list_feeds shows them.

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

Input Schema

NameRequiredDescriptionDefault
urlNoA new address.
feedYesThe feed's id, title or address.
titleNoA new name.
categoriesNoThe categories it is in from now on (replaces the old ones; [] for none).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is largely supplied. The description adds little beyond that—no mention of behavior when the feed is not found, partial updates, or what a failure looks like—leaving the mutation semantics thin relative to what the annotations do not cover.

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?

Two short sentences, action and fields front-loaded, with the sibling pointer as a trailing clarification. Nothing is padded and every clause carries information about what can be changed.

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?

For a four-parameter, non-nested mutation tool with full schema coverage and no output schema, the description plus annotations give an agent enough to invoke it correctly. The remaining gap is edge-case behavior (unknown feed, partial update semantics), which is minor here but keeps it from a 5.

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%, with per-parameter text explaining the address, name, and category replacement (including '[] for none'). The description merely restates that same field list, adding no extra meaning such as format, uniqueness constraints, or precedence when both title and url are changed.

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—'Rename a followed feed, change its address, or replace its categories'—enumerating exactly the three mutations the schema's optional fields allow. It also distances the tool from the read sibling by noting 'list_feeds shows them,' so an agent can distinguish it from list_feeds and add_feed without inspecting schemas.

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?

Clear usage context: this is the edit tool for an existing follow, covering renames, address changes, and category replacement, with list_feeds implicitly the way to discover the target. It stops short of explicit when-not guidance (e.g., use add_feed to follow a new feed, update_folder for folders), so it is not a full 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources