Skip to main content
Glama

Embed code for the face shape widget

get_embed_snippet
Read-only

Returns paste-ready HTML (a div plus one script tag) that adds the free face shape finder to a web page at the chosen size, with the usage terms and the embed page URL. The widget measures the visitor's photo in their browser, no sign-up and no upload to this server; the terms ask for the visible credit link to stay. Use this when a website owner wants photo measurement on their page; for one person's own photo, point them to thefaceanalysis.com/face-shape-detector instead (this server accepts no photos), and use classify_face_shape when you already have the four distances. Read-only; it only generates text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_embed_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoWidget width: compact (360px), standard (480px) or wide (720px). Default standard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / size / description
      Previous value: -"compact 360px, standard 480px, wide 720px"New value: +"Widget width: compact (360px), standard (480px) or wide (720px). Default standard."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds meaningful context beyond that: the widget runs in the visitor's browser, no photo is uploaded to this server, no sign-up is required, and the usage terms require a visible credit link. It also states that the tool only generates text, which reinforces the read-only behavior without contradicting the 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?

The description is front-loaded with what the tool returns, followed by behavioral context and routing guidance. Despite being several sentences, every sentence adds useful information for selection or correct use, with no redundant restatement of the name or title.

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 single fully documented enum parameter, existing annotations, and lack of an output schema, the description is complete. It covers the return form, privacy behavior, terms, and alternatives, leaving no material gaps for correct invocation.

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 description coverage is 100%, and the enum plus width values are fully documented in the schema itself. The description mentions the chosen size but does not add details beyond what the schema already provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: it returns paste-ready HTML containing a div and script tag for the face shape widget. It also explicitly distinguishes this from classify_face_shape and from the external site, so an agent can identify the tool without checking siblings.

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?

It gives explicit when-to-use guidance for website owners and clear when-not guidance for individual photo measurement, routing that case to thefaceanalysis.com. It also names classify_face_shape as the alternative when the four distances are already available.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.