Skip to main content
Glama

render_component

Renders UI components to screenshots across Chromium, Firefox, and WebKit without a dev server. Built-in Tailwind CSS support for quick visual verification.

Instructions

Instantly render a React/Vue/HTML component and return screenshots across browser engines. Zero setup needed — just pass your code. Tailwind CSS is built-in. Use this to visually verify UI code without starting a dev server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesComponent code to render
frameworkNoFramework: html, react, vue, or sveltereact
enginesNoBrowser engines to render in. Use ["chromium","firefox","webkit"] for cross-browser check.
widthNoViewport width (px)
heightNoViewport height (px)
fullPageNoCapture full scroll height
darkModeNoRender with Tailwind dark mode (adds 'dark' class to html)
colorSchemesNoRender both: ["light","dark"] returns 2 screenshots for comparison
cssNoCustom CSS to inject (design tokens, variables, etc)
tailwindVersionNoTailwind CSS version (3 or 4)3
mockNoMock network responses. Keys: URL pattern (path '/api/users', glob '**/api/*', or full URL). Values: response body (auto-serialized as JSON) or { status, contentType, body, headers }.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses instant rendering, zero setup, built-in Tailwind, and multi-engine screenshots, but doesn't cover failure modes, rate limits, or whether it's read-only. The core behavior is well communicated.

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?

Three concise sentences front-loaded with the core action and key features. No redundant or wasted words.

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

Completeness2/5

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

Despite 11 parameters, the description omits critical context about return format (e.g., how screenshots are returned) and does not mention optional features like mocking, custom CSS, or color schemes. Lacks completeness for a complex tool without output schema.

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 100%, so baseline is 3. The description adds minimal value beyond the schema (e.g., 'Tailwind CSS is built-in' aligns with tailwindVersion param). No new semantic insight.

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 clearly states it renders a component and returns screenshots across browser engines. It distinguishes from sibling tools like render_catalog or render_grid by focusing on single-component verification without a dev server.

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 gives context to use it for visual verification of UI code and notes zero setup, but does not explicitly mention when not to use it or compare to alternatives like render_catalog for multiple components.

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/kamegoro/frameshot'

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