Transistor-MCP

publish_episode

Set an episode's status to published, scheduled, or draft, enabling separate control over publish state without altering metadata.

Instructions

Publish, schedule, or unpublish an episode. Use this to change an episode's publish status separately from updating its metadata.

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": {
      "episode_id": "<episode_id>",
      "status": "<status>"
    },
    "name": "publish_episode"
  }
}

Input Schema

Name	Required	Description
`status`	Yes	New status: 'published' to publish now, 'scheduled' to schedule for a future date, 'draft' to unpublish
`episode_id`	Yes	ID of the episode
`published_at`	No	Date/time to publish or schedule (in the podcast's time zone). Required when status is 'scheduled'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 25, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description must cover behavior. It lists three statuses and mentions schedule requires future date (via parameter description), but lacks details on side effects, prerequisites, or idempotency.

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?

Two concise sentences, front-loaded with action verb and key intent. No unnecessary words or repetition.

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?

Adequate for a simple 3-parameter tool with no output schema. Covers status changes and separation from metadata update. Could mention that published_at is required when scheduled, but schema already does.

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 covers 100% of parameters with descriptions. Description adds little beyond enumerating statuses and mentioning separate usage; baseline 3 is appropriate.

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?

Clearly states verb-resource pair (publish/schedule/unpublish an episode) and explicitly distinguishes from updating metadata, differentiating from sibling tool update_episode.

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?

Explicitly tells when to use (changing publish status separately from metadata) and implies not for metadata updates. No explicit when-not but context from siblings is enough.

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