Transistor-MCP

get_download_summary

Retrieve computed download analytics for a show or episode. Get total downloads, daily average, week-over-week trend, and best/worst days without manual calculations.

Instructions

Get a computed download summary for a show or episode. Returns total downloads, daily average, week-over-week trend, and best/worst days — no manual calculation needed.

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_download_summary"
  }
}

Input Schema

Name	Required	Description
`show_id`	Yes	ID of the show
`end_date`	No	End date (accepts yyyy-mm-dd or dd-mm-yyyy) (optional)
`episode_id`	No	ID of a specific episode (optional, omit for show-level stats)
`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.7/5.0

Behavior3/5

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

The description does not disclose authentication requirements, rate limits, or side effects. It implies a read operation but does not explicitly state read-only behavior. Without annotations, more context on behavior would be beneficial.

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 sentences, front-loaded with key action and resource, no wasted words. Efficiently conveys purpose and key returns.

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?

The description lists output components but does not detail their format or types. Without an output schema, more completeness on return structure would be helpful. It adequately covers input parameters but lacks output detail.

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 description coverage is 100%, so parameters are well-documented in the schema. The description adds context about output but does not enhance parameter meaning beyond the schema. 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?

The description clearly states the verb 'Get' and resource 'computed download summary for a show or episode', and lists the specific metrics returned (total downloads, daily average, etc.), distinguishing it from broader analytics tools like get_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 implies usage for download summary queries but does not explicitly state when to use this tool over siblings like get_analytics or get_all_episode_analytics. The phrase 'no manual calculation needed' hints at an alternative but lacks explicit guidance.

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