Grep.FM

Get podcast contacts

get_podcast_contacts

DestructiveIdempotent

Contact emails for up to 25 shows, most reliable first (the feed owner's address leads when known).

Each show whose emails are returned counts once toward the user's monthly export quota, the same quota as CSV exports; asking again for a show within 30 days is free, and shows without an email cost nothing. When the quota runs out the remaining shows come back without emails.

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": {
      "podcasts": "<podcasts>"
    },
    "name": "get_podcast_contacts"
  }
}

Input Schema

Name	Required	Description	Default
`podcasts`	Yes	Grep.FM podcast ids.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already flag non-read-only and destructive behavior; the description adds meaningful context by disclosing monthly export quota consumption, the 30-day free re-ask window, zero cost for shows without emails, and partial results when quota runs out. It does not detail authentication needs, but the quota side effect is clearly explained.

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 efficiently adds quota and result behavior. Every sentence carries operational information, and there is no redundant or filler content.

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

Completeness4/5

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

With no output schema, the description does a good job explaining return behavior: emails are ordered by reliability, missing emails are omitted when quota runs out, and shows without emails cost nothing. It stops short of defining exact response fields, but gives enough for an agent to interpret typical results.

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 single `podcasts` parameter is already documented. The description adds value beyond the schema by specifying the maximum of 25 shows and how each show affects quota and results, which helps the agent understand constraints on the input array.

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 states a specific verb-resource pair: retrieving contact emails for podcasts, with clear scope (up to 25 shows) and ordering (most reliable first, feed owner leading when known). It is readily distinguishable from siblings like get_podcast or search_podcasts, which do not focus on contact emails.

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?

Usage context is implied through quota and caching details, but the description never explicitly states when to choose this tool over alternatives such as get_podcast or search_podcasts. It explains quota consumption and free re-asks, yet lacks direct when-to-use or when-not-to-use guidance.

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

All Grep.FM tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?