Skip to main content
Glama

Generate Creative Brief from Image

image_brief
Read-only

Compound endpoint: one image in, full creative brief out. Extracts dominant colours, matches them to the Colour Memory archive with coherent cultural naming, understands the scene, identifies the style period, suggests product directions by category (textiles, interiors, fashion), generates an image generation prompt, and returns a swatch URL. One call covers what palette_extract + palette_analyse + agent_brief do separately. style_context gives coherent archive matching, e.g. 'English cottage garden', 'Victorian', 'MarsColour'. The result already carries the rendered palette and its PNG, PDF, ASE, JSON and CSS downloads, ready to show the customer. The archive anchors a colour was derived from are evidence, not the recommended colours. A final palette chosen from this evidence is registered with palette_finalize, called once with those exact colours, so the customer can see and download what was actually recommended.

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": "image_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNoNumber of colours to extract (3-12, default 6)
modelNoImage model: midjourney | flux | dalle | stable_diffusion (default midjourney)
archiveNoExplicit archive name override e.g. 'MarsColour', 'Japan'
image_urlNoPublic URL of the image
image_base64NoBase64-encoded image data
product_typeNoProduct focus e.g. 'tea towel', 'wallpaper', 'ceramic', 'textile'
grey_card_hexNoHex value from a grey/white card for white balance correction
style_contextNoPlain English style e.g. 'English cottage garden', 'Victorian', 'Japanese', 'MarsColour'. Restricts archive matching to coherent cultural set.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses the full result payload (rendered palette, swatch URL, multiple download formats) and a crucial semantic caveat: archive anchors are evidence, not recommended colours. It also explains the correct downstream workflow through palette_finalize, which prevents an agent from mistaking evidence colours for the final recommendation.

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 front-loaded with the compound purpose and remains information-dense rather than padded. It is somewhat long and repeats schema examples for style_context, but the extra material about output artefacts and palette_finalize is directly useful.

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?

For a complex compound tool, the definition covers purpose, sibling alternatives, output contents, the evidentiary distinction between archive anchors and recommended colours, and the follow-on finalization step. Given full schema coverage and an output schema, the remaining details are adequately carried by structured fields.

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 100%, so the input schema already documents all eight parameters. The description adds useful context around style_context and archive behaviour, but does not add meaning beyond the schema for image input, colour count, model, product_type, or grey-card correction.

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 opens with a specific verb-and-resource framing: 'one image in, full creative brief out.' It then enumerates the concrete outputs (colour extraction, archive matching, scene/style understanding, product directions, prompt, swatch URL) and explicitly contrasts the tool with palette_extract, palette_analyse, and agent_brief.

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

Usage Guidelines4/5

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

It clearly states that this single call replaces several narrower tools and explains the follow-on relationship with palette_finalize. It does not explicitly say when to prefer the narrower sibling tools or when not to use this compound endpoint, so it stops short of full when/when-not guidance.

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.

Resources