Skip to main content
Glama

aaddyy_headshot_generator

Generate professional headshots from portrait photos with customizable backgrounds. Ideal for resumes, LinkedIn, or corporate profiles.

Instructions

Transform portrait photos into professional headshots with customizable backgrounds (~12 credits)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_urlYesPortrait image URL or base64 data URI
aspect_ratioNoAspect ratio in format "width:height" (e.g., "3:4", "1:1"). Backend automatically converts to required format.
background_styleNoprofessional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the approximate credit cost (~12 credits), which is genuinely useful, but says nothing about processing time, permissions, output format, or whether the original image is retained or modified.

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?

One compact sentence that front-loads the core action and appends the cost signal. No wasted words, though it could carry slightly more useful detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter generation tool with no output schema, the description covers the core action and cost but omits return format, latency, and the meaning of the undocumented background_style enum. Adequate but with clear gaps.

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 coverage is 67%, and the description only hints at the background_style parameter via 'customizable backgrounds'. The empty schema description for background_style is not compensated; aspect_ratio is already well documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Transform portrait photos into professional headshots') plus a distinguishing feature (customizable backgrounds). It is clearly separable from siblings like aaddyy_background_remover or aaddyy_image_generator, though it doesn't explicitly name an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose this over the many sibling image tools (background_remover, upscale_image, ghibli_generator, etc.). The credit cost is mentioned, but there is no context on prerequisites or appropriate use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.