Skip to main content
Glama
Sign In

Urlbox

by io.github.urlbox
OverviewDiscussionsAdmin

Set a project's default render options

set_project_defaults
DestructiveIdempotent

Set the default render options a project applies to every render (for example {"block_ads": true, "hide_cookie_banners": true}), replacing any defaults it had. Options passed on a render still win. Pass options as null to clear the defaults. Use describe_options to look up option names.

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>",
      "project": "<project>",
      "options": "<options>"
    },
    "name": "set_project_defaults"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentYesRequired. 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.
optionsYesRender options object, or null to clear. Replaces the stored defaults.
projectYesProject id (proj_…) or exact name. Use list_projects to see them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description earns credit for concretely explaining what the destructive behavior destroys ('replacing any defaults it had') and what clearing means (null). It stops short of covering permissions, auth requirements, or what the call returns, which is the remaining gap.

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?

Four tight sentences, front-loaded with the core action, then precedence, then the clearing case, then the lookup hint. No filler, and the inline example is compact.

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 destructive, three-parameter mutation with no output schema, the description covers replacement semantics, precedence, clearing, and option discovery. What is missing is minor: whether the project must already exist and any hint about the response.

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 coverage is 100%, so the baseline is 3, but the description adds real value: it gives a concrete options payload example ({"block_ads": true, "hide_cookie_banners": true}) and routes the agent to describe_options for valid option names. The intent parameter's analytics/audit role is only explained 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 and resource ('Set the default render options a project applies to every render'), including the effective scope (every render for that project). It also implicitly separates itself from the `render` tool by noting that per-render options override the defaults, and it names `describe_options` as the lookup sibling.

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

Usage Guidelines5/5

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

Gives explicit when-to-use context (setting project-wide defaults), the precedence rule against per-render options ('Options passed on a render still win'), the alternative for discovering option names ('Use describe_options'), and the exact condition for removal ('Pass options as null to clear'). An agent has everything needed to choose this tool over `render` or `update_project`.

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

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