Skip to main content
Glama

new_service_announcement_email

Write a personal client announcement email that introduces a new service, references your relationship, and positions the client as an insider.

Instructions

Write a personal announcement email to an existing client introducing a new service you're now offering. Warmer than cold outreach because you already have a relationship — the goal is to let trusted clients hear first, plant the seed for future work, and feel like insiders. Reads as personal and considered, not a mass newsletter blast. Workflow: draft here → send individually with personalised why_relevant per client. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient's first name
new_serviceYesThe new service you are now offering (e.g. 'quarterly website audits', 'brand identity design', 'video production', 'fractional CMO retainers')
why_relevantNoOptional: why this client specifically might benefit — reference shared history or something you noticed (e.g. 'given the site we built last year, a quarterly audit would catch issues before they compound', 'you mentioned wanting to add video — that's now something I can handle end-to-end'). The more specific, the better.
proof_pointNoOptional: a credibility signal for the new service (e.g. 'I have completed three audits this quarter', 'just wrapped my first brand film for a fintech startup'). Omit if you are launching fresh.
offerNoOptional: any early-access or founding-client incentive (e.g. 'a founding-client rate of $X for the first three months', 'the first audit on me so you can see the format'). Keep it genuine — do not manufacture urgency.
your_nameNoYour name for the sign-off
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses tone ('personal and considered, not a mass newsletter blast'), workflow (individual sending), and a constraint ('does not count against your monthly draft limit'). It also clarifies optional parameter usage for personalization. This is strong behavioral context.

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 several sentences but each sentence adds value: purpose, tone distinction, workflow, parameter notes. It is front-loaded with the core purpose. Slightly verbose but still effective.

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 6 parameters, no output schema, and no annotations, the description covers purpose, tone, workflow, and parameter guidance thoroughly. It provides enough context for an agent to use the tool appropriately. Minor gaps: no mention of expected response or error cases.

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?

All 6 parameters have schema descriptions (100% coverage), so the schema already defines each parameter. The description adds only light context (e.g., 'optional: why relevant...') but doesn't provide new semantic insight beyond what the schema offers. Baseline 3 is appropriate.

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's purpose: writing a personal announcement email to an existing client about a new service. It specifies the relationship context and goal ('let trusted clients hear first'), distinguishing it from cold outreach or mass newsletters. The verb 'write' and resource 'announcement email' are specific.

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 explicitly says 'warmer than cold outreach because you already have a relationship,' indicating when to use it (existing clients) and contrasting with cold pitches. It also provides workflow guidance ('draft here → send individually'). However, it does not list specific alternative tools or scenarios to avoid.

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