Skip to main content
Glama

Sponsors of a podcast

get_show_sponsors

Who sponsors a given podcast. Returns every brand whose ad read was detected in that show's transcribed episodes, with how many reads, whether they were host-read or network-inserted, and when they were first and last heard. Accepts a show title, a trackpodcasts.com slug or a URL. If the title is ambiguous it returns candidate shows to choose from instead of guessing. Detected ad reads only — brands that were merely mentioned are not included.

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

Input Schema

NameRequiredDescriptionDefault
showYesPodcast title, slug or trackpodcasts.com URL, e.g. "The Glenn Beck Program".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it explains the returned fields, ambiguity behavior, and inclusion criteria. It does not discuss permissions, rate limits, or error behavior, which keeps it below the highest level for a no-annotation tool.

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 front-loaded with the core purpose and then adds only useful details: return contents, accepted input forms, ambiguity handling, and inclusion criteria. Every sentence contributes without repetition.

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

Completeness5/5

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

For a one-parameter read tool with no annotations or output schema, the description provides enough detail about inputs, returned data, ambiguity handling, and exclusions for an agent to call it correctly.

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%, so the schema already documents the single show parameter. The description adds meaningful semantics beyond the schema by clarifying accepted title/slug/URL forms and the ambiguity-resolution behavior.

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 states a specific query: who sponsors a given podcast, returning every brand whose ad read was detected. It clearly distinguishes detected ad reads from mere mentions, but it does not explicitly differentiate this show-to-brand lookup from the sibling get_brand_podcasts tool.

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?

It gives clear use context and an exclusion: detected ad reads only, not brands merely mentioned. It also explains ambiguity handling by returning candidate shows rather than guessing, though it does not explicitly name the sibling alternative for reverse brand-to-podcast lookup.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources