Skip to main content
Glama

guest_post_pitch

Compose a reader-first guest post pitch that opens with a tailored article angle, establishes credibility, and ends with a frictionless ask to increase acceptance.

Instructions

Write a cold pitch email to a blog, newsletter, or publication asking to contribute a guest article. Guest posts build SEO authority, earn backlinks, and put your name in front of an established audience — but most pitches are rejected because they lead with the writer's ego, not the editor's interests. This generates a reader-first pitch that opens with a concrete article angle tailored to the publication's audience, briefly establishes your credibility, and ends with a frictionless ask. Distinct from podcast_pitch_email (audio appearances), conference_talk_pitch (in-person speaking), and cold_pitch (client sales). Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
publication_nameYesName of the blog, newsletter, or publication you are pitching to (e.g. 'Smashing Magazine', 'Freelancer Union Blog', 'Indie Hackers')
article_angleYesThe specific article topic or angle you are proposing — frame it as value for the publication's readers, not a showcase for you (e.g. 'how freelancers can write proposals that close without discounting', 'the three scope conversations every new freelancer gets wrong')
editor_nameNoOptional: first name of the editor or content lead — personalises the opener. Omit if unknown.
why_their_readersNoOptional: one sentence on why this topic is a specific fit for this publication's readership — concrete beats vague (e.g. 'your readers are mostly early-career freelancers navigating their first client contracts', 'Indie Hackers readers are shipping and selling — scope creep is their number-one frustration'). Omit to keep the pitch tight.
your_credentialNoOptional: your single most relevant credibility signal — specific beats vague (e.g. '9 years of freelance product design, 80+ client engagements', 'I built ProposalCraft, used by 600+ freelancers', 'my last piece on Toptal got 12k shares'). Omit if you have no strong signal yet.
proposed_titleNoOptional: a working headline for the article — hooks the editor immediately. Omit to keep the pitch angle open.
your_nameNoOptional: your name for the sign-off
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses the tool generates a reader-first pitch with specific structure (angle, credibility, frictionless ask) and notes it does not count against the monthly draft limit. No contradictions or hidden behaviors are evident, though details like character limits or formatting are absent.

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 moderately concise, using multiple sentences to convey purpose, context, structure, and sibling distinctions. Every sentence adds value, but it could be slightly shorter without losing clarity. It is front-loaded with the core action.

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?

Given the tool has 7 parameters and no output schema, the description is fairly complete: it explains the input purpose, output structure (pitch email), and extra benefits (draft limit). Missing details like output format (plain text vs. HTML) might affect completeness slightly, but overall it is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 7 parameters have schema descriptions, and the tool description adds significant meaning beyond them—e.g., for 'article_angle', it emphasizes framing as value for readers, not self-showcase. This extra guidance helps the agent use parameters effectively.

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 this tool writes a cold pitch email for guest articles, with a specific verb ('Write a cold pitch email') and resource ('blog, newsletter, or publication'). It explicitly distinguishes from three sibling tools (podcast_pitch_email, conference_talk_pitch, cold_pitch), making purpose and boundaries very clear.

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?

The description explains when to use the tool (for SEO, backlinks, audience building) and provides guidance on what makes a good pitch (reader-first, not ego-driven). It names alternative tools for different contexts. However, it does not explicitly state when NOT to use this tool beyond the sibling distinction, leaving some ambiguity.

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