Skip to main content
Glama

AgentSearch Screenshot

agentsearch_screenshot
Read-onlyIdempotent

Take a screenshot of a public web page in a real headless browser and return it as an MCP image (PNG or JPEG) plus JSON metadata. Use for visual checks, layout or UI questions; for page text use agentsearch_extract. Free, no wallet: this remote server uses the AgentSearch free relay. Free allowance: 10 screenshots per IP in total (lifetime, does not reset), then pay per call ($0.004). Read-only: it loads the page like a browser visit. The page shown is untrusted third-party content.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute public http(s) URL to capture.
formatNoImage format, default png.
viewportNoViewport in CSS pixels.
full_pageNoCapture the whole page (clipped at 4000 px) instead of the viewport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover readOnly/openWorld/idempotent/destructive, and the description adds material context beyond them: a lifetime free allowance of 10 screenshots per IP, a per-call price of $0.004 after that, the free-relay nature of the remote server, and a warning that the rendered page is untrusted third-party content. The 'Read-only: it loads the page like a browser visit' line is consistent with readOnlyHint=true and clarifies what the operation actually does on the wire.

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

Conciseness4/5

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

Front-loaded with the core action and return type, then usage routing, then cost/quota, then a safety note, with no filler sentences. It is somewhat dense, packing pricing, quota, and trust warnings into a compact block, but each sentence carries distinct information an agent needs.

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?

No output schema exists, and the description compensates by naming the return shape (image plus JSON metadata) and the available formats. It also covers the quota/pricing model and the untrusted-content caveat, which are the non-obvious risks for this tool. Only minor gaps remain, such as whether the JSON metadata is returned alongside or separately and how quota exhaustion surfaces as an error.

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 url, format, viewport, and full_page are already fully documented in the schema, and the description adds no syntax or default detail beyond it. The 4000 px full-page clipping limit is the one behavioral constraint worth noting, but it is already carried in the schema's full_page description. Baseline 3 applies when the schema does the heavy lifting.

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 concrete verb and resource ('Take a screenshot of a public web page in a real headless browser') plus the return type (MCP image PNG/JPEG plus JSON metadata). It also explicitly distinguishes itself from agentsearch_extract by saying text extraction belongs there, so an agent can route correctly without opening a 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?

Gives an explicit when-to-use ('visual checks, layout or UI questions') and an explicit alternative with its own condition ('for page text use agentsearch_extract'). That is a complete routing rule rather than an implied one.

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.