inbox-preview

get_screenshot

Fetch a rendered screenshot. Returns the image URL for the given job, client, width, and environment (color scheme / images).

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": {
      "job_id": "<job_id>",
      "client": "<client>",
      "viewport_width": "<viewport_width>"
    },
    "name": "get_screenshot"
  }
}

Input Schema

Name	Required	Description	Default
`client`	Yes	Client ID
`job_id`	Yes	The job ID
`color_scheme`	No	The render's color scheme	light
`viewport_width`	Yes	Viewport width of the render, matching the job (1280 when the job used client defaults)
`images_disabled`	No	Whether the render had images blocked

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 8, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedJul 28, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the return value (image URL) but does not state whether the operation is read-only, any side effects, authentication requirements, rate limits, or error behavior. The lack of explicit safety information lowers the score.

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?

The description is two short sentences with no filler or redundancy. It front-loads the primary action and return value, making it easy to parse quickly.

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?

Given the full schema coverage and the simple nature of the tool, the description is sufficient. It states what the tool does and what it returns. There is no output schema, but the return type is implied as a URL, which is adequate for this context.

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% for all 5 parameters, so the baseline is 3. The description paraphrases the parameters ('width' for viewport_width, 'environment' for color_scheme/images_disabled) but adds little novel explanation beyond the schema's own descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb ('Fetch') and resource ('rendered screenshot'), and mentions it returns the image URL. Sibling tools like get_job, list_clients, and submit_preview are distinct enough that the purpose is unambiguous, though it does not explicitly contrast with them.

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

Usage Guidelines2/5

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

Provides no guidance on when to use this tool instead of siblings. It does not mention any triggering conditions, prerequisites, or alternative scenarios, leaving the agent to infer usage from the parameter list alone.

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

All inbox-preview 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.

Resources

Need Help?