Skip to main content
Glama

Compose asset

compose_asset
Read-only

Crop any image to a format's exact pixel size and bake on a headline, CTA and logo, e.g. to move a reframed crop or try new copy on an existing render without paying for a new one. Returns a URL to the PNG. With brand_id, blank copy fields take the kit's defaults.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image_url": "<image_url>",
      "format": "<format>"
    },
    "name": "compose_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctaNo
cropNoWhere the format's window sits on the image. Omit for a centred crop.
brandNoThe full brand, only when there is no kit for it. brand_id is simpler.
formatYes
overlayNo
brand_idNoA brand kit from list_brands (id or name). Brings the colours, fonts, logo, website and default copy (headline, call to action, small print); use instead of brand.
headlineNo
image_urlYes
small_printNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses the return value (a URL to the PNG) and a non-obvious precedence rule: with brand_id, only blank copy fields fall back to the kit's defaults, so explicit values win. The cost hint ("without paying for a new one") is useful behavior the annotations do not carry. It stops short of stating whether the call is synchronous or whether the produced render is persisted or listed elsewhere.

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?

Three sentences, front-loaded with the operation, then the motivating scenarios, then the return value and defaults rule. No filler, though the "e.g." scenario clause is slightly dense for the space it occupies.

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?

For a nine-parameter compositing tool with no output schema, the description covers the core operation, the output shape (PNG URL), and the brand-id fallback semantics. Remaining gaps are secondary: credit consumption, whether the result is stored, and guidance on the copy fields that the schema only bounds by length.

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 33% across nine parameters with nested objects, so the description should compensate more than it does. It clarifies brand_id versus brand indirectly via the defaults rule, but adds nothing about headline, cta, small_print, overlay, or format beyond their names. Baseline for a partially documented schema is a 3.

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?

"Crop any image to a format's exact pixel size and bake on a headline, CTA and logo" is a specific verb stack against a specific resource, and the two example scenarios (reframed crop, new copy on an existing render) pin down the intent. It does not name or contrast any sibling (e.g. add_graphic, generate_assets), so the last point of differentiation is left implicit.

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?

The sentence "to move a reframed crop or try new copy on an existing render without paying for a new one" gives clear positive triggers, including a cost-based motivation that helps the agent prefer this over re-rendering. There are no explicit when-not conditions or named alternatives for cases like generating a brand-new asset from scratch.

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