Skip to main content
Glama

Render a Seedwall image

render
Read-onlyIdempotent

Generate stable SVG and PNG URLs from a Seedwall look, plus an editable studio link and preview, for hero backgrounds, OG images, banners, blog covers, or wallpapers.

Instructions

Renders a look at any size and returns stable SVG and PNG URLs, a link to keep editing it in the Seedwall studio, and a small preview image. Use it for website heroes, section backgrounds, OG/social images, banners, blog covers, or wallpapers.

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": {
      "look": "<look>"
    },
    "name": "render"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookYesLook id from list_looks
seedNoVaries the random layout while keeping the look; same seed = same image
themeNoRecolour with a syntax theme id from list_looks (e.g. nord, dracula, github-light)
widthNoPixels; default 1920
deviceNoDevice id from list_looks instead of width/height
heightNoPixels; default 1080
paramsNoParam overrides from describe_look, e.g. {"bg":"#0b1020","levels":30}. Invalid values are ignored.
presetNoPreset id; defaults to the look's first preset
previewNoInclude a small PNG preview in the result
text_freeNoHide the look's built-in text. Use true for backgrounds that sit behind your own content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety and repeatability profile is covered. The description adds genuinely new behavioral context beyond that: the returned URLs are described as stable, and an edit link plus preview are returned by default. It does not cover persistence lifetime of renders, auth requirements, or any rate/cost limits, which keeps it at 4.

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?

Two sentences, no filler, and the return contract is front-loaded before the use-case list. Every clause earns its place by either describing output or narrowing application.

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 ten-parameter render tool with a nested params object and no output schema, the description usefully describes what comes back (URLs, edit link, preview), which is the main gap a missing output schema would otherwise leave. Remaining gaps are minor: precedence between device and width/height, error behavior for unknown look ids, and render lifetime.

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% across all ten parameters, including the nested params object and the preview/text_free flags, so the schema carries the semantics. The description only echoes "at any size" and "small preview image," adding no syntax, precedence rules (e.g. device vs width/height), or override behavior beyond what is documented in the schema. Baseline 3 applies.

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?

The description names a specific verb and resource ("Renders a look") and goes further by enumerating the return payload: stable SVG and PNG URLs, a studio edit link, and a small preview image. That is far more specific than the title alone. It stops short of a 5 because it never distinguishes this tool from siblings like list_looks or describe_look, leaving the agent to infer that those are discovery tools.

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?

Concrete use cases are supplied (heroes, section backgrounds, OG/social images, banners, blog covers, wallpapers), which tells the agent the kind of request this tool answers. There are no exclusions or explicit alternative routing, so it falls short of the 5 bar that requires when-not guidance.

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

Deploy Server

Other Tools