Skip to main content
Glama

Preview what the person will see

previewRequest
Read-only

Renders the form or approval card exactly as a recipient sees it, at phone (390 px) and desktop (1280 px) width, and returns screenshots plus plain-language lint (contrast, long labels, missing help), and previewUrl, which opens the same page in a browser. Takes the form or approval fields of createRequest (no audience, expiresIn, webhookUrl or metadata), plus viewports and sampleData. Useful before creating a form many people will see.

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": {
      "mode": "<mode>",
      "title": "<title>"
    },
    "name": "previewRequest"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
themeNoColours, font and layout: https://runitby.app/llms.txt ("Theme").
titleYes
localeNoLanguage of the hosted page and its emails, optionally with a region for dates, like "es-AR". Write the title and questions in the same language.
schemaNoJSON Schema (type object) for forms. Supported types, formats, widgets and limits: https://runitby.app/llms.txt ("Schema subset").
approvalNo
sectionsNo
requesterNoHow your agent introduces itself, e.g. "Ava (the Acme refunds agent)".
viewportsNoScreenshot widths: 390 (phone) and/or 1280 (desktop).
sampleDataNoAnswers to prefill, to see how filled fields look.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a safe, read-only, non-destructive operation. The description goes beyond that by naming concrete outputs (screenshots, plain-language lint, previewUrl) and listing createRequest fields it deliberately omits, which helps the agent avoid invalid calls. It stops short of stating explicitly that no request is created.

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 dense sentences with no filler. The primary behavior and outputs are front-loaded, and the secondary sentence carries the parameter relationship and usage guidance without repetition.

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 10-parameter tool with nested objects and no output schema, the description does the important work of describing outputs and input constraints. It does not explain how form mode versus approval mode differ, or whether previews expire, but the schema covers the required fields.

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

Parameters4/5

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

Schema description coverage is only 60%, but the description compensates by explaining the relationship to createRequest and the deliberate exclusion of audience, expiresIn, webhookUrl and metadata. It also mentions viewports and sampleData, though those are already documented in the schema.

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 ('Renders') and resource ('the form or approval card'), plus the exact output and widths. It is immediately distinguishable from createRequest, which it explicitly references as the source of its input fields.

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?

Gives a clear use case: 'Useful before creating a form many people will see,' which routes the agent to preview rather than create. It does not name when *not* to use it or which sibling to call instead for other preview-like needs, but the context is strong.

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