Skip to main content
Glama

partnership_outreach

Craft a referral partnership email to a complementary service provider, proposing a mutual client referral arrangement to generate warm inbound leads.

Instructions

Write a peer-to-peer outreach email to a complementary service provider — a designer reaching out to a copywriter, a developer to a designer, a consultant to an agency. Proposes a referral partnership where you both send clients each other's way. Warm, not transactional, under 150 words. Referral partnerships are one of the highest-ROI growth moves a freelancer can make — one good partner can generate years of warm inbound. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recipient_nameYesTheir first name
recipient_serviceYesWhat they do (e.g. 'copywriting', 'brand strategy', 'UX design', 'paid ads', 'SEO')
your_serviceYesWhat you do (e.g. 'web design', 'mobile development', 'social media management')
shared_client_typeYesThe type of client you both serve (e.g. 'SaaS startups', 'e-commerce brands', 'professional services firms', 'small creative agencies')
connection_hookNoOptional: how you found them or what specifically caught your attention (e.g. 'saw your work on the Acme rebrand', 'we have a mutual client in the fintech space', 'came across your portfolio via LinkedIn'). Makes the email feel specific rather than templated.
your_nameNoOptional: your name for the sign-off
Behavior4/5

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

No annotations provided, so description bears full burden. It discloses a non-obvious behavioral trait: 'Does not count against your monthly draft limit.' It also specifies tone ('Warm, not transactional') and length ('under 150 words'). No contradictions.

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?

Description is 5 sentences, efficiently conveying purpose, usage, tone, and special trait. It front-loads the core action. Slightly verbose with the ROI statement, but not wasteful.

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?

No output schema, but the tool's output is a generated email, which is self-explanatory. Description covers purpose, target audience, tone, and constraints. It is complete for the agent to understand the tool's function and result.

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. Description adds value for parameters like 'connection_hook' explaining its purpose ('Makes the email feel specific rather than templated') and 'recipient_service' giving examples. All required parameters are explained adequately.

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?

Description clearly states the tool writes a peer-to-peer outreach email for referral partnerships, with specific verb 'Write' and resource 'outreach email'. It distinguishes from sibling tools like referral_request by specifying the target (complementary service provider) and purpose (proposing a referral partnership).

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?

Description gives clear context on when to use: for outreach to complementary providers for referral partnerships, with examples of professional pairs. It does not explicitly state when not to use or mention alternatives, but the context is sufficient for an agent to select it among siblings.

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