Skip to main content
Glama

Podcasts a brand sponsors

get_brand_podcasts

Which podcasts a brand advertises on. Returns the shows where that brand's ad reads were detected, newest first, with the exact total even when the list itself is truncated for the plan. Accepts a brand name, slug or domain (a domain is the most reliable). Returns candidate brands when the name is ambiguous.

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": {
      "brand": "<brand>"
    },
    "name": "get_brand_podcasts"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesBrand name, slug or domain, e.g. "Squarespace" or "squarespace.com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses ordering ('newest first'), a non-obvious truncation behavior ('the exact total even when the list itself is truncated for the plan'), and the degenerate-input outcome (candidate brands on ambiguity). It does not cover auth or rate limits, but the key behavioral surprises are surfaced.

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?

Three short sentences, each earning its place: purpose, return behavior, then input forms and the ambiguity fallback. Nothing is repeated from the title or schema verbatim.

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?

There is no output schema, so the description must explain return values — it does so (matching shows, newest-first order, exact total, plan-based truncation, candidate-brand fallback). For a single-parameter read tool this is everything an agent needs to call and interpret it.

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 baseline is 3; the description earns above that by adding that domains are the most reliable form and that an ambiguous name yields candidate brands rather than a failure. That is decision-relevant meaning the schema does not carry.

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?

States a specific verb and resource ('Which podcasts a brand advertises on') plus the scope of what's returned ('shows where that brand's ad reads were detected'). The direction of the relationship (brand → shows) is unambiguous and implicitly opposite to get_show_sponsors, so an agent can route correctly.

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?

Gives clear usage context for the input ('accepts a brand name, slug or domain') with a preference ranking ('a domain is the most reliable'), and defines fallback behavior ('returns candidate brands when the name is ambiguous'). It never names a sibling as an alternative for cases where the agent actually wants show→brand data, so it stops short of full when-to-use/when-not guidance.

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