HTML/CSS to Image API

Create a batch of images

create_batch_images

Destructive

Creates multiple image assets from shared default_options and individual variations. Call get_max_batch_size first and keep the number of variations within the returned plan limit; a limit of 0 requires individual image calls. Each variation overrides corresponding defaults. Returns per-image asset IDs, URLs, and format information in item. Use the individual creation tools when only one image or an inline preview is needed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`variations`	Yes	Individual image variations, any parameter supplied will override the corresponding option in default_options.
`default_options`	No	Optional common parameters that will apply to all images in the batch.

Output Schema

TableJSON Schema

Name	Required	Description
`item`	No	Operation result. Check success before using this value.
`error`	No	Error details when the operation failed; null on success.
`success`	No	Whether the operation succeeded. If false, inspect error before retrying.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 2, 2026

addedInput schema / properties / default_options / default
```
Added value: +null
```

changedInput schema / properties / default_options / description

Previous value: -"Common parameters that will apply to all images in the batch."New value: +"Optional common parameters that will apply to all images in the batch."

changedInput schema / required

Previous value: -[
-  "default_options",
-  "variations"
-]New value: +[
+  "variations"
+]

Changed2 schema fields changedSep 29, 2026

addedInput schema / properties / default_options / properties / request_overrides

Added value: +{
+  "description": "An array of request rules. Use `action: \"block\"` with a `url` wildcard pattern (using `*`) and/or `resource_types` as an array of resource names, such as `image`, `script`, or `xhr`. Both matchers must match when supplied together; any matching block rule blocks the request. Omitted, `null`, or `[]` adds no overrides. Requires a paid plan. Accepts a JSON array in JSON requests or a JSON-encoded array string in form requests. Maximum 100 rules and 512 characters per URL pattern. Each block rule requires a nonempty URL pattern or at least one resource type; supplied matchers cannot be empty. Not supported in query strings.",
+  "items": {
+    "anyOf": [
+      {
+        "properties": {
+          "action": {
+            "const": "block"
+          },
+          "resource_types": {
+            "description": "Resource types to match, supplied as an array of names, such as image, script, xhr, or fetch. Any listed type may match. When url is also supplied, it must match too.",
+            "items": {
+              "enum": [
+                "beacon",
+                "document",
+                "stylesheet",
+                "image",
+                "image_set",
+                "media",
+                "font",
+                "script",
+                "text_track",
+                "xhr",
+                "fetch",
+                "event_source",
+                "manifest",
+                "ping",
+                "img",
+                "other"
+              ],
+              "type": "string"
+            },
+            "type": [
+              "array",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "URL wildcard pattern to match, using * for any sequence of characters. When resource_types is also supplied, both matchers must match.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        }
+      }
+    ],
+    "description": "A browser request override. The action discriminator selects the rule type; currently only block is supported.",
+    "required": [
+      "action"
+    ],
+    "type": [
+      "object",
+      "null"
+    ]
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedInput schema / properties / variations / items / properties / request_overrides

Added value: +{
+  "description": "An array of request rules. Use `action: \"block\"` with a `url` wildcard pattern (using `*`) and/or `resource_types` as an array of resource names, such as `image`, `script`, or `xhr`. Both matchers must match when supplied together; any matching block rule blocks the request. Omitted, `null`, or `[]` adds no overrides. Requires a paid plan. Accepts a JSON array in JSON requests or a JSON-encoded array string in form requests. Maximum 100 rules and 512 characters per URL pattern. Each block rule requires a nonempty URL pattern or at least one resource type; supplied matchers cannot be empty. Not supported in query strings.",
+  "items": {
+    "anyOf": [
+      {
+        "properties": {
+          "action": {
+            "const": "block"
+          },
+          "resource_types": {
+            "description": "Resource types to match, supplied as an array of names, such as image, script, xhr, or fetch. Any listed type may match. When url is also supplied, it must match too.",
+            "items": {
+              "enum": [
+                "beacon",
+                "document",
+                "stylesheet",
+                "image",
+                "image_set",
+                "media",
+                "font",
+                "script",
+                "text_track",
+                "xhr",
+                "fetch",
+                "event_source",
+                "manifest",
+                "ping",
+                "img",
+                "other"
+              ],
+              "type": "string"
+            },
+            "type": [
+              "array",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "URL wildcard pattern to match, using * for any sequence of characters. When resource_types is also supplied, both matchers must match.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        }
+      }
+    ],
+    "description": "A browser request override. The action discriminator selects the rule type; currently only block is supported.",
+    "required": [
+      "action"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

Changed2 schema fields changedSep 22, 2026

changedInput schema / properties / default_options / properties / disable_twemoji / description

Previous value: -"Use native Linux emoji rendering instead of HCTI's consistent Twemoji images. Leave `disable_twemoji` unset unless native emoji rendering is specifically needed."New value: +"HTML/CSS images use Twemoji by default; set `disable_twemoji: true` to disable it. URL images inject Twemoji only with explicit `disable_twemoji: false`; omitted, null, or true leaves the page's emoji handling unchanged."

changedInput schema / properties / variations / items / properties / disable_twemoji / description

Previous value: -"Use native Linux emoji rendering instead of HCTI's consistent Twemoji images. Leave `disable_twemoji` unset unless native emoji rendering is specifically needed."New value: +"HTML/CSS images use Twemoji by default; set `disable_twemoji: true` to disable it. URL images inject Twemoji only with explicit `disable_twemoji: false`; omitted, null, or true leaves the page's emoji handling unchanged."

Changed3 schema fields changedSep 15, 2026

addedOutput schema / properties / error / description

Added value: +"Error details when the operation failed; null on success."

addedOutput schema / properties / item / description

Added value: +"Operation result. Check success before using this value."

addedOutput schema / properties / success / description

Added value: +"Whether the operation succeeded. If false, inspect error before retrying."

First observedSep 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is carried structurally. The description adds genuinely useful behavior beyond them: the default/variation merge rule and the plan-limit gating via get_max_batch_size. It does not elaborate on what the destructive aspect means for existing assets, which keeps it short of a 5.

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?

Five short sentences, each carrying a distinct load: purpose, prerequisite, limit rule, merge semantics, and return shape, with the alternative-tool guidance last. Nothing is padded and the primary purpose is front-loaded.

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 two-parameter tool with a full output schema, the definition covers everything an agent needs: the prerequisite call, the limit-0 fallback, the override relationship, the response fields (item), and the sibling alternative. Return-value details are not required since an output schema exists, yet the brief mention adds orientation without bloat.

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 schema's own variations description already states that supplied parameters override default_options, so the description's merge sentence largely repeats structured data. It adds the useful batch-level framing but no new per-parameter syntax or constraints, matching the baseline for fully documented schemas.

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 ('Creates multiple image assets') and immediately frames the two-parameter model (shared default_options + individual variations). It also names the sibling alternative ('individual creation tools'), so an agent can distinguish it from create_image and create_url_image without opening schemas.

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

Usage Guidelines5/5

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

Explicit prerequisites and routing rules: 'Call get_max_batch_size first', a returned limit of 0 means fall back to individual image calls, and single-image or inline-preview needs should use the individual tools. This covers when-to-use, when-not-to-use, and which alternative to pick.

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

All HTML/CSS to Image API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.