Skip to main content
Glama

gaents

job_site_render

Render a website's pages in a real browser

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": {
      "url": "<url>"
    },
    "name": "job_site_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespattern https://\S{4,500}
max_resultsNodefault 3, at most 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full behavioral burden and falls well short. It does not say whether rendering is read-only, how long a render takes, whether there are rate limits or costs, what happens on failure, or whether pages are crawled following links (the max_results cap hints at crawling but is never explained).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with zero waste and the core concept front-loaded, but for a tool with no annotations and no output schema the terseness reads as under-specification rather than efficiency.

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?

With no annotations and no output schema, the description must explain what a render returns (extracted text, HTML, screenshot?), how many pages, and the cost/time profile. None of that is present, so an agent cannot predict the result or the expense of calling it.

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%, so the regex pattern for url and the "default 3, at most 20" bound for max_results are already documented. The description adds no additional meaning about what max_results counts (pages? results per page?) or how the URL pattern constrains input, so baseline 3 applies.

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 specific verb ("Render") and resource ("a website's pages") plus the key qualifier "in a real browser", which signals JS-capable rendering rather than a plain fetch. It is clear on its own, though it does not name or differentiate against any sibling, which is a minor gap since the visible siblings operate on different domains.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The phrase "in a real browser" faintly implies use for JS-heavy or blocked pages, but the agent must infer that condition entirely rather than being told it.

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