Skip to main content
Glama

cold_pitch_follow_up

Write a concise follow-up for unanswered cold pitches. Resurface your key offer, give an easy out, and request a simple yes or no.

Instructions

Write a short, professional follow-up when a cold pitch has gone unanswered. Shorter than the original pitch — brevity signals confidence. Doesn't repeat everything; just resurfaces the key hook, gives an easy out, and asks for one yes/no. Distinct from client_followup (which is for post-proposal follow-up after a prospect showed interest) and win_back_email (re-engaging a lapsed client). This is for genuine cold silence — they never replied at all. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recipient_nameYesFirst name of the person you're following up with
company_nameNoOptional: company name — helps personalise the subject line
original_pitch_summaryYesOne-sentence summary of what you offered in the original pitch (e.g. 'UX help for your onboarding flow', 'copywriting for your pricing page rewrite', 'React development for the mobile app')
days_since_pitchNoOptional: how long ago you sent the original pitch (e.g. 7, 14, 21). Used to calibrate tone — shorter gap = lighter touch, longer gap = slightly more direct.
new_angleNoOptional: something new to add that wasn't in the original pitch — a relevant observation, a result you can now reference, a question that reframes the value. Omit if you have nothing genuinely new to say.
your_nameNoYour name for the sign-off
Behavior4/5

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

With no annotations, the description covers behavioral aspects: it generates a concise follow-up, resurfaces key hook, gives an easy out, asks yes/no, and mentions the draft limit. Lacks mention of any potential side effects or constraints beyond that.

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?

Description is front-loaded with purpose and key guidelines. Every sentence adds value; no redundancy. Efficiently communicates usage, tone, and sibling distinction.

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?

Given no output schema, the description still explains enough about output (short follow-up). Parameters are well-explained, and sibling tools are clearly differentiated. Completeness is high for the tool's complexity.

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%, baseline 3. The description adds context for days_since_pitch (calibrates tone) and new_angle (optional addition). Also clarifies that company_name personalizes subject line and original_pitch_summary is a one-sentence summary.

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?

Clearly states it writes a short professional follow-up for unanswered cold pitches. Distinguishes from client_followup and win_back_email by specifying the exact scenario (genuine cold silence).

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?

Explicitly defines when to use (cold pitch unanswered) and when not (post-proposal follow-up, re-engaging lapsed clients). Additionally provides a behavioral hint about not counting against draft limits.

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