Skip to main content
Glama
cshum

Imagor MCP

Official

render_template

Compile a layout of text, image, and rect slots at a given canvas size into one imagor URL, with text fitted to boxes and placeholders filled.

Instructions

Render a layout at a given canvas size. Geometry is written the way imagor writes it, so slots can be positioned and sized relative to the canvas with full and full-N, and one template then serves several sizes. A text slot given a height is fitted with fit_text against the box its geometry resolves to, because a font size is absolute and would otherwise be relatively smaller on a larger canvas. Values fill {{placeholders}}. Returns the path, the URL, and what each slot resolved to. Verify it before handing it over - imagor answers 200 with the image unchanged when a filter does not apply, so a render that reports success is not a render that is right. For one image with typed parameters and no layout, use build_imagor_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotsYesthe elements, applied in order, so later slots draw over earlier ones
valuesNovalues for {{placeholders}} in slot text and image fields
backgroundNocanvas background, for example color:1a1a2e; defaults to color:white
canvas_widthYescanvas width in pixels
canvas_heightYescanvas height in pixels

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
modeYes
noteNo
pathYes
signedYes
resolvedYes
absolute_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.10
    • changedInput schema / properties / slots / items / properties / filters / description
      Previous value: -"for image or rect: filters applied to this slot's own source, written without the filters: prefix, e.g. smart/filters:round_corner(230,230,fff)"New value: +"for image or rect: filters applied to this slot's own source, colon-separated, for example smart():round_corner(230,230,fff). The filters: prefix is added for you. Measured: a slash between filters 404s"
    • changedInput schema / properties / slots / items / properties / slots / items / properties / filters / description
      Previous value: -"for image or rect: filters applied to this slot's own source, written without the filters: prefix, e.g. smart/filters:round_corner(230,230,fff)"New value: +"for image or rect: filters applied to this slot's own source, colon-separated, for example smart():round_corner(230,230,fff). The filters: prefix is added for you. Measured: a slash between filters 404s"
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does real work: it discloses the return contents (path, URL, resolved slots) and a critical silent-failure mode ('imagor answers 200 with the image unchanged when a filter does not apply, so a render that reports success is not a render that is right'). It also explains the fitting behavior and placeholder substitution. Gaps: no permission/auth requirements and no other error semantics.

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?

Front-loaded with the purpose, then geometry, fitting, placeholders, return, the verification warning, and the alternative in a sensible order; no filler sentences. The middle sentences are dense and somewhat convoluted ('fitted with fit_text against the box its geometry resolves to'), but each carries information an agent needs.

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 complex tool with a deeply nested object schema and no annotations, the description supplies the essential behavioral warning (200 does not mean correct) and the fitting/geometry model that the schema alone does not convey as a coherent whole. An output schema exists, so the brief mention of returns is acceptable. It does not cover auth or failure classes beyond the 200 gotcha.

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 parameter docs are exhaustive, so the schema already carries the meaning; baseline is 3. The description reinforces the geometry notation ('full and full-N') and the text-fitting rationale, but those largely restate what the per-property descriptions already say, adding little net new per-parameter information.

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?

States a specific verb and resource — 'Render a layout at a given canvas size' — and immediately distinguishes itself from the sibling 'build_imagor_url' by scope (multi-slot layout vs. one image with typed parameters). An agent can tell this apart from parse_template and build_imagor_url without opening any schema.

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?

Explicitly names an alternative and the condition that selects it: 'For one image with typed parameters and no layout, use build_imagor_url.' It also prescribes a workflow ('Verify it before handing it over'). It does not address the other siblings (parse_template, fit_text), so it stops short of full alternative routing.

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