Skip to main content
Glama

testimonial_request_email

Write emails requesting client testimonials or reviews after project completion. Offers three approaches: post-completion ask, platform-specific review request, or delayed follow-up.

Instructions

Write the email asking a client for a testimonial or review after a completed project. For when you want to capture a happy client's feedback while the experience is fresh — the kind of social proof that closes the next deal without any extra selling. Three routes: after_completion (default — clean ask at the end of a project; tone is warm and low-pressure, makes it easy to say yes, offers to draft something for them to edit which removes the friction of starting from scratch), specific_platform (you need a review on a specific platform — Google, LinkedIn, Clutch, G2, Trustpilot — because that's where your next prospects look; routes the client to the right place without making it feel like an errand), delayed_ask (you finished the project weeks or months ago and forgot to ask, or didn't feel it was the right moment at the time; acknowledges the gap without apologising excessively, still low-pressure). Distinct from client_reference_request_email (asking someone to speak with a prospect by phone/video, not provide a written quote). Does not count against your monthly draft limit. Required: client_name. Optional: project_name (helps personalise — 'the Westbrook website rebrand', 'your new brand identity'), platform (for specific_platform route — e.g. 'Google', 'LinkedIn', 'Clutch', 'Trustpilot'), platform_url (direct link to the review page — if provided, makes the ask one click), offer_draft (set to true to offer to write a draft for them to edit — removes friction; implied on after_completion), route ('after_completion' | 'specific_platform' | 'delayed_ask' — default after_completion), your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient first name
project_nameNoOptional: name of the project — e.g. 'the Westbrook website', 'your brand identity', 'the content strategy'. Personalises the ask.
platformNoFor specific_platform route: the review platform you want them to use — e.g. 'Google', 'LinkedIn', 'Clutch', 'G2', 'Trustpilot'.
platform_urlNoFor specific_platform route: direct URL to the review page — e.g. your Google review link. Makes the ask one click for the client.
offer_draftNoOptional: set to true to offer to write a draft testimonial for the client to edit. Removes the main friction point (starting from scratch). Implied on after_completion route.
routeNoafter_completion (default) — fresh ask at project close, warm and low-pressure; specific_platform — request a review on a named platform with a direct link; delayed_ask — following up weeks or months after the project ended.
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 the full burden. It explains the three behavioral variations (routes) and the tone for each, along with the draft offer behavior. However, it does not specify whether the email is saved or sent automatically, which could be relevant for an AI agent.

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 relatively long but well-structured, with clear sections for each route and parameter context. It could be slightly more concise, but the detail is justified given the three distinct use cases.

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?

Without an output schema, the description does not explicitly state the return value, but it is implied that the tool generates an email draft. The parameter details are thorough, covering required and optional fields with examples. Overall, it is complete for the given 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%, so the baseline is 3. The description adds value by providing context for the 'route' enum values, explaining implied behavior for 'offer_draft' on the after_completion route, and clarifying the purpose of 'platform_url'. This goes beyond the schema descriptions.

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 testimonial request email and specifies three distinct routes (after_completion, specific_platform, delayed_ask). It differentiates from the sibling tool client_reference_request_email by noting it's for a written quote rather than a phone/video conversation.

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?

Explicit guidance on when to use each route, including the context for each. Additionally, it states the tool does not count against the monthly draft limit and distinguishes from a sibling tool, providing clear alternatives.

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