Transistor-MCP

create_subscribers_batch

Bulk add subscribers to a private podcast by providing a show ID and list of email addresses, with an option to skip welcome emails.

Instructions

Add multiple subscribers to a private podcast at once

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": {
      "show_id": "<show_id>",
      "emails": "<emails>"
    },
    "name": "create_subscribers_batch"
  }
}

Input Schema

Name	Required	Description
`emails`	Yes	Array of subscriber email addresses
`show_id`	Yes	ID of the private podcast
`skip_welcome_email`	No	Skip sending welcome emails (default false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 25, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description must carry full burden. It indicates a write operation but lacks details on side effects, limits (e.g., max emails), error handling, or confirmation of success.

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?

Single sentence, no redundant information, and front-loaded. Efficient but could be slightly more structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a batch operation with 3 parameters and no output schema, the description misses important context like max batch size, duplicate handling, and return value. Not fully complete.

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%, so baseline is 3. The description adds no additional meaning to parameters beyond what is already in the schema.

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?

The description clearly states the verb 'Add' and the resource 'multiple subscribers to a private podcast', indicating batch creation. It distinguishes from the sibling 'create_subscriber' by implying batch operation with 'at once'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like create_subscriber. The description only implies batch use but does not specify constraints or comparisons.

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