Urlbox

List recent renders

list_renders

Read-only

List recent renders, newest first: each with its id, status, target URL, project, result URL and, for failures, the reason. Filter by project, status, start date or URL; page through older renders with page/nextPage. Pass a renderId to get_render for timings, options and full details.

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": {
      "intent": "<intent>"
    },
    "name": "list_renders"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page of results, newest first. When hasMore is true, call again with nextPage.
`limit`	No
`since`	No	ISO date or datetime; only renders created at or after it.
`intent`	Yes	Required. In one or two sentences, what you are trying to achieve for the user with this call and why (for example: 'Screenshot the pricing page so the user can compare plans'). Recorded for analytics and audit; do not include secrets.
`status`	No
`project`	No	Project id (proj_…) or exact name. Defaults to every project your key can see.
`url_contains`	No	Only renders whose target URL contains this text.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: result ordering, the exact fields returned, failure reasons being included, and that older results are reached via page/nextPage rather than a different tool.

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?

A single dense sentence, front-loaded with the action and ordering, then the return shape, then filters, then paging, then the sibling pointer. Every clause carries information; nothing is wasted.

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?

With no output schema, the description correctly compensates by enumerating returned fields and explaining how to page forward. Filter coverage is complete for the schema's filter parameters; only the limit default and the hasMore/nextPage mechanics are left implicit.

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 71%, so the schema carries most parameter meaning; the description restates the filter axes (project, status, start date, URL) without adding syntax or format detail. It adds a little on pagination (page/nextPage) but says nothing about limit or the required intent parameter beyond what the schema already documents.

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 (list renders) with ordering (newest first) and enumerates the returned fields, so the agent knows exactly what comes back. It also distinguishes itself from get_render, which handles full details for a single render.

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?

Names the alternative (get_render) and the condition that selects it (timings, options, full details), and lists the four filter dimensions that narrow the list. It lacks an explicit 'do not use this when…' exclusion, but the routing to the sibling is clear.

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

All Urlbox 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.