Skip to main content
Glama

portfolio_consent_email

Draft an email requesting client permission to feature their project in your portfolio, with options for simple listing, showing work samples, or writing a case study.

Instructions

Write the email asking a client for permission to feature their project in your portfolio — the ask most freelancers either skip (and get caught out later) or make feel bigger than it needs to be. Three routes: add_to_portfolio (default — asking to name the client and list the project type in your portfolio; lowest-friction ask, single question, done in under 60 words), show_work_samples (asking to display actual screenshots, documents, or design files publicly — needs specific approval because you're sharing their outputs; names exactly what you want to show), full_case_study (requesting to write a detailed breakdown with results, metrics, or outcomes — warrants a slightly longer email with what you'd say and a clear opt-out so it doesn't feel like an obligation). Distinct from testimonial_request_email (asking them to write or approve a quote about you) and case_study_outline (an internal document structure). Does not count against your monthly draft limit. Required: client_name. Optional: project_name (helps the client know which project you mean), sample_description (for show_work_samples: what you want to show — e.g. 'the homepage, two interior pages, and the mobile screens'), results_to_share (for full_case_study: the metrics or outcomes you want to highlight — e.g. '40% faster proposal turnaround'), portfolio_url (where their work would appear — makes the ask concrete), route ('add_to_portfolio' | 'show_work_samples' | 'full_case_study' — default add_to_portfolio), your_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesClient first name
project_nameNoOptional: project name or type — e.g. 'the website redesign', 'your brand identity project'. Helps the client know which work you mean.
sample_descriptionNoOptional (show_work_samples route): what specifically you want to show publicly — e.g. 'the homepage, two interior pages, and the mobile screens', 'three proposal documents with company name visible'.
results_to_shareNoOptional (full_case_study route): the metrics or outcomes you want to highlight — e.g. '40% faster proposal turnaround', 'launched on time within budget, positive client feedback'. Keep it factual.
portfolio_urlNoOptional: URL where their work would appear — makes the ask concrete and lets them see how their work would be presented.
routeNoadd_to_portfolio (default) — name and list the project; show_work_samples — show actual screenshots or files publicly; full_case_study — write a detailed breakdown with results.
your_nameNoOptional: your 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 behavioral disclosure. It explains the three functional routes and optional parameters that modify output, but does not explicitly state whether the tool sends the email or only drafts it. This slight ambiguity prevents a perfect score.

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 thorough but somewhat verbose, consisting of several sentences that could be tightened. However, it is well-structured with clear separation of routes and parameters, and front-loads the core purpose effectively.

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 the tool has 7 parameters, no output schema, and no annotations, the description is remarkably complete. It covers all parameter details, explains each route's purpose, and provides examples, leaving little ambiguity for an AI agent.

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?

The description adds substantial value beyond the input schema, providing examples and context for each parameter (e.g., sample_description, results_to_share, portfolio_url, route). Schema coverage is 100%, and the description enriches understanding with concrete usage scenarios.

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 an email asking for portfolio consent, specifies three distinct routes (add_to_portfolio, show_work_samples, full_case_study), and distinguishes it from sibling tools like testimonial_request_email and case_study_outline. The verb 'write' and resource 'email' are explicit.

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?

The description explains when to use each route (lowest friction, specific approval, detailed breakdown) and explicitly contrasts with sibling tools. It also notes that the tool does not count against monthly draft limits, providing clear context for when to invoke it.

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