Transistor-MCP

get_all_episode_analytics

Retrieve analytics for all episodes of a show, with optional date range filters to narrow down the period.

Instructions

Get analytics for all episodes of a show. Defaults to last 7 days if no dates provided.

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>"
    },
    "name": "get_all_episode_analytics"
  }
}

Input Schema

Name	Required	Description
`show_id`	Yes	ID of the show to get analytics for
`end_date`	No	End date (accepts yyyy-mm-dd or dd-mm-yyyy) (optional)
`start_date`	No	Start date (accepts yyyy-mm-dd or dd-mm-yyyy) (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 25, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only discloses the default date behavior but omits other important traits such as whether the operation is read-only, required permissions, or rate limits.

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?

The description is a single, front-loaded sentence with no unnecessary words, efficiently conveying the tool's purpose and key behavior.

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?

Given the absence of an output schema, the description should explain the return format (e.g., list of episode analytics). It does not, leaving a significant gap in understanding what the tool provides.

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% with descriptions for all three parameters. The description adds value by explaining the default date behavior for start and end dates, going beyond the schema's format specification.

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 action (Get analytics) and the specific resource (all episodes of a show), distinguishing it from the sibling tool 'get_analytics' which likely covers show-level analytics.

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?

The description provides implicit usage context by noting the default date range of last 7 days, but it does not explicitly state when to use this tool over alternatives or when not to use it.

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