Skip to main content
Glama
Podcast MCP
by calebn

feed_write

Write the episode's feed.xml file next to its exported audio, refused while feed_read reports blockers. Idempotent: repeat calls with no changes write nothing.

Instructions

Write the episode's feed file (<name>.feed.xml) next to its exported audio.

Refused while feed_read shows a blocker, such as no show, no hosting address or no exported MP3. Idempotent: a second call with nothing changed writes nothing. The export job also writes it. Returns the path, the files written and the file state.

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

Input Schema

NameRequiredDescriptionDefault
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses refusal conditions, idempotency, a side-effect writer (the export job), and return contents. It still leaves some mutation semantics implicit, such as whether an existing feed is overwritten and whether any special permissions are required.

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 front-loaded with the core action, then adds blockers, idempotency, side effect, and return shape in compact sentences. There is little wasted wording, and the structure supports quick scanning.

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 no annotations, one optional parameter, and an existing output schema, the description covers purpose, refusal conditions, idempotency, side effects, and return shape. The notable completeness gap is that the sole input parameter is never explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, ``project_path``, has 0% schema description coverage and is not mentioned at all in the description. An agent must infer its meaning, effect, and default purely from the parameter name and ``default: null``.

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?

Names the exact artifact written (``<name>.feed.xml``), where it is written (next to exported audio), and the write action. It also ties the operation to ``feed_read`` for blocker checking, which helps distinguish it from read/config siblings.

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?

States a clear precondition: it is refused while ``feed_read`` shows blockers such as no show, no hosting address, or no exported MP3. It also notes that the export job writes the same file, but it does not explicitly say when a manual ``feed_write`` is preferable to that job or how it relates to ``feed_set``/``feed_unset``.

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