Skip to main content
Glama

availability_announcement_email

Draft a warm, personal email to past clients announcing your upcoming availability for new projects, using the provided availability window. Helps freelancers quickly reconnect and secure new work without sounding desperate.

Instructions

Write a short, warm email to past clients or contacts announcing that you have upcoming availability for new project work. One of the highest-ROI freelancer marketing moves: a brief, personal note to people who already know your work often surfaces a project within days. Gets the tone right: confident, not desperate — you're sharing news, not asking for a favour. Required: availability_window (e.g. 'from July 1', 'starting mid-August', 'a couple of slots opening next month'). Optional: recipient_name (personalises the opening), services_offered (what you're available for — defaults to your usual work), project_type (narrow the ask: 'short-term projects', 'ongoing retainers', 'one-off design work'), max_projects (e.g. '1 or 2 projects' — signals scarcity without pressure), cta (what you want them to do: 'reply if you have something in mind', 'forward this to someone who might need help' — defaults to reply), your_name. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
availability_windowYesWhen you'll be available (e.g. 'from July 1', 'starting mid-August', 'a couple of slots opening next month')
recipient_nameNoOptional: first name of the recipient — personalises the greeting. Omit for a generic version.
services_offeredNoOptional: what you do (e.g. 'copywriting and content strategy', 'UX design', 'backend development'). Defaults to your usual work.
project_typeNoOptional: narrow the ask (e.g. 'short-term projects', 'ongoing retainers', 'brand identity work', 'one-off builds')
max_projectsNoOptional: signals scarcity (e.g. '1 or 2 projects', 'a couple of spots', 'one retainer slot')
ctaNoOptional: what you want them to do (e.g. 'reply if you have something in mind', 'forward to anyone who might need help', 'book a quick call'). Defaults to reply.
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 disclose all behavioral traits. It describes the tone (confident, not desperate) and the fact it doesn't count against draft limits. However, it lacks details on output (draft vs send), authentication requirements, or rate limits. The behavioral disclosure is partial.

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 concise and well-structured: it leads with purpose, contextualizes the value, gives tone guidance, then lists parameters. Every sentence is necessary and adds value. No redundancy.

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?

For a 7-param tool without output schema or annotations, the description covers purpose, tone, parameter details, and a limit note. It is missing explicit description of the output (e.g., the generated email text). This is a minor gap but overall complete enough for an AI agent to use correctly.

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?

Schema description coverage is 100%, so baseline is 3. The description adds value by grouping parameters as required/optional and providing examples (e.g., availability_window examples). However, it mostly reiterates the schema descriptions without adding significant new semantics.

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 the tool writes a short, warm email to past clients/contacts announcing availability. It distinguishes from siblings like annual_review_email or bid_lost_follow_up by focusing on availability announcement. The high-ROI context further clarifies its specific use case.

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 provides context on when to use (when you have upcoming availability) and notes it's high-ROI. It mentions it does not count against monthly draft limit. However, it does not explicitly exclude scenarios or mention alternatives 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