Skip to main content
Glama

podcast_pitch_email

Generate a host-first podcast pitch that emphasizes audience benefit, references a specific episode, and includes a low-friction ask.

Instructions

Write a compelling cold pitch to appear as a guest on a podcast. Podcast appearances are a powerful freelancer marketing channel — authority-building, warm inbound leads, and backlinks — but most pitches are generic and get deleted within seconds. This generates a host-first pitch that leads with why their audience wins (not why you want exposure), references a specific episode to prove you're a genuine listener, and ends with a concrete, low-friction ask. Distinct from conference_talk_pitch (formal CFP submission for in-person events) and cold_pitch (client sales outreach). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
podcast_nameYesName of the podcast you are pitching to appear on (e.g. 'Freelance to Founder', 'The Futur')
host_nameYesFirst name of the podcast host (e.g. 'Chris', 'Paul')
episode_angleYesThe specific topic or angle you are pitching — frame it as a benefit for listeners, not a feature about you (e.g. 'why most freelancers lose deals before the proposal even lands', 'the one-page scope framework that ends scope creep arguments')
why_their_audienceYesWhy this topic is specifically valuable for this podcast's listeners — be concrete (e.g. 'your audience of creative freelancers deals with scope creep weekly; I've spoken to 200+ of them', 'your listeners are trying to move from project to retainer work — I made that shift and can walk through it step by step')
your_credentialYesYour single most relevant credibility signal — specific beats vague (e.g. '8 years of freelance UX, 120+ client contracts', 'built ProposalCraft, an open-source MCP tool with 500+ installs', 'went from $0 to $180k/yr freelancing in 3 years')
episode_referenceNoOptional: a specific recent episode you listened to — title or guest name — and one sentence on what resonated. Proves you're a genuine listener, not a spray-and-pray pitcher. Omit if you haven't listened to a recent episode.
your_nameNoOptional: your name for the sign-off
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It states the tool 'generates' a pitch, implying it is a content generation tool, but does not disclose whether it sends emails, saves drafts, or has side effects. The behavioral traits are partially covered but lack completeness.

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?

The description is concise at about 80 words, with a clear structure: purpose, context, differentiation, and a notable fact (draft limit). Every sentence adds value, though it could be slightly more efficient without losing content.

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 explains the purpose and strategy well, but it lacks specification of what the tool returns (e.g., full email text, subject line). Given the absence of an output schema and moderate complexity, the description is sufficient but not fully complete.

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?

The input schema has 100% description coverage, so the baseline is 3. The main description adds strategic context that indirectly helps understand parameter usage, but it does not provide additional meaning beyond the schema descriptions for individual parameters.

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 uses a specific verb 'Write' and resource 'cold pitch to appear as a guest on a podcast', clearly stating the tool's function. It explicitly distinguishes itself from sibling tools 'conference_talk_pitch' and 'cold_pitch', ensuring no ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the tool (for podcast guest pitches), provides context on why generic pitches fail, and explicitly contrasts with alternative tools. It also mentions that it does not count against monthly draft limits, offering additional usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jabbawocky/proposalcraft'

If you have feedback or need assistance with the MCP directory API, please join our Discord server