Skip to main content
Glama

PostPod

Create show

create_show

Create this account's daily podcast show from X accounts and topics. Fails if a show already exists. Language defaults to English. Free accounts stay English only and can follow 3 accounts. Pro can follow 25. Nora is the free voice. Leo, Kristine, Ken, and Marko need Pro for the daily show. 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": {
      "handles": "<handles>",
      "voice": "<voice>",
      "timezone": "<timezone>",
      "delivery_hhmm": "<delivery_hhmm>"
    },
    "name": "create_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses the duplicate-show failure, the plan gating on voice and handle count, the English-only default, and that the subscription is not modified. These are exactly the operational facts an agent needs before a mutating call.

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?

Front-loaded with the core action and the failure condition, then tier constraints in short declarative sentences. A couple of clauses restate schema content (voice names, language default), which costs a little against strict economy but keeps the definition self-contained.

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 an 8-parameter mutating tool with no output schema, the description covers preconditions, plan limits, defaults, and side effects, which is most of what is needed. It does not say whether creation triggers a first episode or what the response contains, leaving a modest gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds constraint semantics the schema lacks: which voices require Pro, that free accounts are English-only, and the 3- vs 25-handle caps. It still says nothing extra about timezone or delivery_hhmm beyond the schema's own text.

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 states a specific verb and resource ("Create this account's daily podcast show") plus the source of its content ("from X accounts and topics"). The failure condition "Fails if a show already exists" implicitly separates it from update_show, but no sibling is named outright.

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 tells the agent the preconditions and failure mode (one show per account, plan-tier limits on handles and voices) which helps decide feasibility. It never states when to prefer update_show or get_show instead, so the routing guidance is only implied.

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