Skip to main content
Glama

Screenshot

screenshot
Read-only

Capture a rendered screenshot of any webpage. Returns the image as base64 with its format, its own width and height (a full-page capture is as tall as the page) and its size in bytes. Use to see how a page looks. To read its text use scrape. Cost: 1 credit, charged only when a call succeeds.

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": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to capture.
widthNoViewport width.
formatNoOutput format.png
heightNoViewport height.
full_pageNoCapture full scrollable page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/non-destructive annotations by disclosing the return payload (base64 image, format, width/height, byte size), a full-page sizing caveat, and a cost model with a success-only billing condition. This is exactly the operational context an agent needs before calling a paid, open-world network 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?

Four short sentences, front-loaded with the action, then the return shape, then the routing guidance, then cost. No redundant restatement of the name or schema fields; every sentence adds information.

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

Completeness5/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 carries the return-value burden and does so fully (encoding, format, dimensions, size) while also covering cost and sibling routing. Nothing an agent needs in order to call this correctly is missing.

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 parameter baseline is 3. The description adds meaning beyond the schema by clarifying that a full-page capture's height reflects the whole scrollable page, which changes how an agent should interpret the returned dimensions versus the viewport height parameter.

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 ("Capture a rendered screenshot of any webpage") and immediately contrasts with the sibling that handles text ("To read its text use scrape"). An agent can distinguish this from scrape without inspecting either schema.

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?

Explicitly frames the use case ("Use to see how a page looks") and names the alternative plus the condition that selects it ("To read its text use scrape"). The routing decision is fully resolved in the description.

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.