Skip to main content
Glama

Argoshot

Render HTML to an image or PDF

render_html
Read-onlyIdempotent

Renders an HTML and CSS string (an Open Graph card, an invoice, a template) to an image or PDF in a real browser. Resources the HTML loads from the web are fetched. Each render counts against the account's plan.

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": {
      "html": "<html>"
    },
    "name": "render_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesThe HTML document or fragment, with its CSS
detailNo
formatNoDefault png
optionsNoAny other option of the API by name; see the API options documentation
viewport_widthNo
viewport_heightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the description only needs to add context beyond that. It adds two genuinely useful facts: external web resources in the HTML are fetched (explaining the open-world behavior's implications), and each render consumes plan quota (a cost/rate consideration). It stops short of anything about latency, caching, or output size limits.

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 short sentences, front-loaded with the core action, then the external-fetch caveat and the billing note. No filler, though the billing sentence could arguably sit after a brief mention of output shape.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter tool with 50% schema coverage, no output schema, and a nested free-form 'options' object, the description leaves meaningful gaps: what a render returns (URL vs inline image, per 'detail'), and what 'options' permits. The quota note covers cost but not result shape.

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 50%, so the schema carries part of the load: html, format and options are documented, while detail, viewport_width and viewport_height have enums/bounds but no prose. The description adds nothing about the meaning of 'detail' modes or viewport effects, so half the parameters remain semantically thin.

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 ('Renders an HTML and CSS string ... to an image or PDF in a real browser') and distinguishes itself from siblings by taking raw HTML rather than a URL or page. The parenthetical examples (Open Graph card, invoice, template) make the intended input concrete.

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

Usage Guidelines3/5

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

The description implies when to use it — when you have an HTML/CSS string to convert — but never explicitly contrasts with siblings like screenshot_url or page_to_pdf, which handle URLs/pages instead. The agent must infer the routing rule from the input type.

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