Skip to main content
Glama

portfolio_request_email

Ask past clients for permission to feature their project in your portfolio or case studies. Specify what you want to show, where it will appear, and offer a preview before publishing.

Instructions

Write the email asking a past client for permission to feature their project in your portfolio, website, or case studies. Specifies exactly what you want to show, where it will appear, and offers them a preview before it goes live. Gives an easy out if they'd rather not — or offers to anonymise the work instead. Distinct from testimonial_request (asking for a quote) and case_study_outline (writing the case study itself) — this is the consent ask that must happen first. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesFirst name or full name of the client
project_nameYesName of the project you want to feature
portfolio_locationYesWhere the work will appear (e.g. 'my portfolio website', 'a case study on my site', 'proposals to prospective clients')
specific_workNoOptional: the specific piece you want to show (e.g. 'the homepage design', 'the brand identity system', 'before-and-after screenshots'). Makes the ask concrete and limits ambiguity.
offer_previewNoOptional: if true (default), offers to share a draft of the portfolio entry before publishing so the client can approve the copy.
offer_anonymiseNoOptional: if true, offers to remove the client's name/branding if they prefer privacy while still allowing the work to be shown.
your_nameNoOptional: your name for the sign-off
Behavior4/5

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

Discloses key behaviors: offers preview and anonymize, gives easy out, and doesn't count toward draft limit. Lacks details on whether it sends the email or just drafts it, but otherwise transparent.

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?

Single paragraph with effective front-loading of purpose. Concise with no wasted words, though could be slightly more structured.

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?

Covers usage context, differentiation from siblings, and an important side note (draft limit). Lacks explicit mention of output format or actions taken, but sufficient for an email generation tool.

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 covers all parameters with descriptions. The tool description adds context about how parameters are used (e.g., specific_work makes ask concrete) but doesn't significantly deepen parameter meaning beyond schema.

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 the tool writes an email asking for permission to feature a project, with specific content details. Distinctly separates from sibling tools testimonial_request and case_study_outline.

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 (consent ask that must happen first) and when not (use testimonial_request or case_study_outline instead). Also notes it doesn't count against 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