Skip to main content
Glama

PostPod

Update show

update_show
Idempotent

Replace the daily show's name, X accounts, topics, language, voice, timezone, and delivery time. The same plan limits as create apply. topic_apply fills accounts from topics up to the Free or Pro cap. 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

NameRequiredDescriptionDefault
idYesShow id.
nameNoShow name. A blank name uses the default.
voiceYesNarrator display name or lowercase id: Nora, Leo, Kristine, Ken, or Marko.
topicsNoSuggested topics: news, sports, ai, finance, or crypto. Listeners pick X accounts and topics. PostPod picks the posts.
handlesYesPublic X accounts to follow, without the @ sign. topic_apply replace fills this list from topics, up to the Free cap of 3 or the Pro cap of 25.
languageNoLanguage code. Defaults to English (en). Free accounts stay English only. Pro can use any supported language.
timezoneYesIANA timezone, for example America/New_York.
topic_applyNoreplace or add fills handles from topics, using the Free cap of 3 accounts or the Pro cap of 25. Omit it to store topics without changing handles.
delivery_hhmmYesDelivery time on the hour or half-hour, 24-hour HH:MM.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a non-destructive, idempotent write (destructiveHint=false, idempotentHint=true), and the description adds genuinely new behavior: plan-tier caps on handles and the explicit guarantee that the subscription is not modified. The main undisclosed trait is what happens to omitted optional fields under "Replace" semantics (reset to default vs. preserved) — a meaningful gap for a replace-style mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the field list, followed by constraints. Every sentence earns its place except the slightly vague "The same plan limits as create apply," which is only clarified by the following sentence.

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 9-parameter, 5-required mutation with no output schema, the definition covers purpose, caps, and one important side-effect exclusion. It leaves ambiguous whether omitted optional parameters (name, topics, language) are cleared or retained, which materially affects how an agent should call it, and gives no hint of the response shape.

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 100% and the schema already spells out caps, enums, timezone format, voice options, and topic_apply's replace/add behavior in detail. The description largely restates that same cap/topic_apply interaction rather than adding syntax or edge-case meaning. Baseline 3 is appropriate when the schema carries the semantics.

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 uses a specific verb ("Replace") plus the resource ("the daily show") and enumerates the mutable fields (name, X accounts, topics, language, voice, timezone, delivery time). That is enough to distinguish it from read siblings like get_show/list_shows. It stops short of explicitly contrasting with create_show, which is the real alternative an agent must choose between.

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?

Useful context is given: plan limits mirror create, topic_apply fills handles up to the Free (3) or Pro (25) cap, and the subscription is untouched. That last clause implicitly routes subscription changes elsewhere. However, there is no explicit statement of when to call update_show versus create_show or get_show, so the agent must infer the update-vs-create choice.

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