Skip to main content
Glama
RenderForm

renderform-mcp

Official
by RenderForm

render_image

Renders images, PDFs, or videos from a RenderForm template by merging dynamic content. Provide a template ID and data to customize the output.

Instructions

This tool renders an image, PDF or video from a RenderForm template.

  • Provide 'template' (required): the template ID, e.g. template_1234.

  • Provide 'data' to merge dynamic content into the template. Keys follow the 'componentId.property' convention (e.g. { "my-text.text": "Hello World!", "my-image.src": "https://example.com/image.jpg" }).

  • Component IDs and editable properties can be discovered with the 'get_template' tool (see the 'properties' field of the template).

  • Optionally provide 'fileName', 'webhookUrl' (called when the render finishes), 'version' (cache key - reusing it returns a cached result instead of re-rendering), 'metadata' (passed through to the webhook), 'batchName' (to group renders together) and 'waitTime' (delay before rendering, max 5000ms).

  • Use 'output: json' (default) to get back a JSON object with the href of the rendered file. Avoid 'output: image' here since it returns raw binary bytes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoData to be merged into the template. Keys follow the 'componentId.property' convention, e.g. { 'my-text.text': 'John' }.
outputNoOutput format. 'json' (default) returns a JSON object with the href of the rendered file, which is recommended here. 'image' returns raw image bytes and is not suitable for text responses.
versionNoCache key used for caching the rendered output. Reusing the same version returns the cached file.
fileNameNoName of the file to be returned (without extension).
metadataNoAdditional metadata to be passed to the webhook.
templateYesTemplate ID to render, e.g. template_1234.
waitTimeNoWait time in milliseconds before rendering (max 5000).
batchNameNoBatch name used for grouping renders together.
webhookUrlNoWebhook URL to be called when the render is done.
Behavior3/5

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

The description adds behavioral details like caching via version, webhook callback, batch grouping, and wait time. Annotations indicate non-read-only and non-destructive. A contradiction exists: description suggests idempotent behavior for same version, but annotations set idempotentHint to false.

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 well-structured with bullet points and front-loads key information. It is slightly verbose but every sentence adds necessary context. Could be more concise without losing clarity.

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 9 parameters, no output schema, and complexity with nested objects, the description covers the rendering workflow, caching, async webhook, retry via version, and warns against using 'output: image'. It sufficiently explains how to use the tool end-to-end.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value by explaining the 'data' key convention, providing examples, and clarifying output format behavior. It also references the 'get_template' tool for component discovery.

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 the tool renders an image, PDF, or video from a RenderForm template, using clear verb and resource. Although the name 'render_image' might suggest only images, the description corrects that. It differentiates from siblings like 'create_pdf' and 'create_screenshot' by specifying template-based rendering.

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 description provides explicit instructions for required and optional parameters, including output format recommendations and how to discover template properties via 'get_template'. However, it does not explicitly state when not to use this tool versus siblings like 'create_pdf'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RenderForm/renderform-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server