Skip to main content
Glama
Sign In
rss-publisher-mcp

rss-publisher-mcp

by bigbatmanorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

republish_entry

Restore an archived or unpublished entry to the active RSS feed by specifying its entry ID.

Instructions

Explicitly revive an archived/unpublished entry into the active feed.

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": {
      "entry_id": "<entry_id>"
    },
    "name": "republish_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the main state transition but does not disclose side effects such as whether history is preserved, whether permissions are required, whether the operation is reversible, or how already-active entries are handled.

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 sentence with no filler, front-loaded with the key action word 'revive.' Every part of the sentence contributes meaning.

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

Completeness3/5

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

For a one-parameter tool with an output schema, the description is close to sufficient, but with no annotations and a large sibling set, it lacks guidance on when alternatives should be preferred and what side effects to expect. It is adequate as a minimal definition but has clear gaps.

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 0%, but the description partially compensates by implying entry_id refers to an archived/unpublished entry. It does not explain the ID format, how to obtain it, or the exact semantics of 'archived' versus 'unpublished,' leaving some inference to the 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 ('revive') and clearly identifies both the source state ('archived/unpublished') and target state ('active feed'). This makes it easy to distinguish from reverse operations like unpublish_entry and from batch operations like publish_batch.

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 'archived/unpublished' qualifier implies when the tool should be used, but there is no explicit when-not-to-use guidance or mention of alternatives. An agent can infer the intended use case, but not the boundary against siblings like publish_batch or correct_entry.

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

Deploy Server

Other Tools