PostPod

Update show

update_show

Idempotent

Replace the daily show's name, accounts, language, voice, timezone, and delivery time. The same plan limits as create apply. This does not change the subscription.

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": {
      "id": "<id>",
      "handles": "<handles>",
      "voice": "<voice>",
      "timezone": "<timezone>",
      "delivery_hhmm": "<delivery_hhmm>"
    },
    "name": "update_show"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Show id.
`name`	No	Show name. A blank name uses the default.
`voice`	Yes	Narrator display name or lowercase id: Nora, Leo, Kristine, Ken, or Marko.
`handles`	Yes	Public X accounts to follow, without the @ sign.
`language`	No	Language code. Defaults to English (en). Free accounts stay English only. Pro can use any supported language.
`timezone`	Yes	IANA timezone, for example America/New_York.
`delivery_hhmm`	Yes	Delivery time on the hour or half-hour, 24-hour HH:MM.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, but the word "Replace" adds important semantics beyond them: the listed fields are overwritten wholesale, not merged. It also discloses two behavioral constraints not in the schema: plan-limit inheritance from create and the fact that the subscription is untouched. Auth requirements and failure behavior for invalid handles remain undisclosed.

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?

Three short sentences, front-loaded with the action and affected fields, followed by the two constraint notes. Nothing is wasted and no sentence merely repeats the tool name.

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 seven-parameter mutation tool with no output schema, the description covers replacement semantics, plan limits, and subscription invariance, which is most of what an agent needs. Minor gaps are what the tool returns and how invalid handles are handled, but the rich schema picks up most of the slack.

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 each parameter documented (voice names, IANA timezone, HH:MM pattern, language defaults), so the baseline is 3. The description mostly restates the field list already present in the schema and adds only the plan-limit note, which marginally reinforces the language restriction.

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 opens with a specific verb ("Replace") and resource ("the daily show") and enumerates the fields being replaced, so an agent can tell this is a full update rather than a partial patch. It references create_show obliquely via "same plan limits as create apply" but does not explicitly contrast with create_show or list_shows.

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?

It gives scope guidance ("same plan limits as create apply") and one exclusion ("This does not change the subscription"), which help the agent understand boundaries. However, there is no explicit statement of when to choose update_show over create_show or get_show, so usage is only implied.

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

All PostPod tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?