Transistor-MCP

get_analytics

Retrieve podcast analytics for a show or episode. Specify a date range or use the default last 14 days to get listening data.

Instructions

Get analytics for a show or episode. Defaults to last 14 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_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)
`episode_id`	No	ID of the episode to get analytics for (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

B3.3/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the default date range behavior (14 days) but does not mention permissions, rate limits, side effects, or the nature of analytics returned.

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?

One clear and efficient sentence. Could be slightly improved with more structure, but it is front-loaded and concise.

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?

No output schema, but parameters are well-covered. The description is minimal and does not specify what analytics metrics are returned (e.g., plays, downloads), leaving some ambiguity for the agent.

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%, but the description adds value by explaining the default behavior for start_date and end_date when omitted, which clarifies parameter semantics beyond the schema.

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 clearly states it gets analytics for a show or episode and mentions the default date range. However, it does not explicitly distinguish itself from siblings like get_all_episode_analytics or get_episode.

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 guidance on when to use this tool versus alternatives such as get_all_episode_analytics, get_episode, or get_show. The description only notes a default behavior but lacks context for decision-making.

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