Skip to main content
Glama

client_satisfaction_survey_email

Draft a warm, brief email to gather client feedback after project completion, with an optional request for a testimonial. Personalize with project outcomes.

Instructions

Write the professional email to send after completing a project — asks the client for feedback and, optionally, a short testimonial. Warm, brief, and non-pushy: makes it easy for a happy client to say yes, and easy for a less-satisfied client to share honest feedback without awkwardness. Distinct from bid_lost_follow_up (you didn't win the work), referral_thank_you (thanking someone who sent a referral), and cold_pitch_follow_up (no response to a pitch) — this is specifically the post-delivery check-in with a client you just delivered work to. Does not count against your monthly draft limit. Required: client_name, project_name. Optional: survey_link (URL to a feedback form — omit to ask directly in the reply), testimonial_ask (if true, adds a short sentence asking for a one or two line testimonial they're happy for you to quote), outcome_note (one sentence on the outcome you delivered, e.g. 'the site went live on schedule' — personalises the email), your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesFirst name of the client
project_nameYesName of the completed project (e.g. 'the Acme brand refresh', 'your Q3 content campaign', 'the checkout redesign')
survey_linkNoURL of a feedback form (e.g. Typeform or Google Form). Omit to ask the client to reply directly.
testimonial_askNoIf true, adds a sentence asking for a short testimonial they are comfortable with you quoting publicly.
outcome_noteNoOne sentence describing a concrete outcome you delivered (e.g. 'the site launched on schedule', 'the campaign hit its target open rate'). Personalises the email — omit to keep it generic.
your_nameNoYour name for the sign-off
Behavior5/5

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

No annotations provided, so description fully covers behavioral traits: tone (warm, brief, non-pushy), handling of happy vs. unsatisfied clients, and optional parameters' effects. No contradictions with missing annotations.

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?

Well-structured: first sentence states core purpose, then details tone, sibling distinctions, and parameter descriptions. No wasted words, all sentences add value.

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, description fully covers tool's purpose, usage, parameters, and behavior. It's complete for correct selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 6 parameters are described in the schema, and the description adds meaning: explains survey_link omission leads to direct reply, testimonial_ask adds a sentence, outcome_note personalizes email, etc.

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's for writing a post-completion feedback email, distinguishing it from similar tools like bid_lost_follow_up, referral_thank_you, and cold_pitch_follow_up. Uses specific verb+resource structure.

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 describes when to use (after completing a project) and names three sibling tools it's distinct from. Also notes it does not count against monthly draft limit.

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