Skip to main content
Glama

Argoshot

Screenshot a web page

screenshot_url
Read-onlyIdempotent

Renders a public web page in a real browser and returns a screenshot: a preview image you can look at, plus a link to the stored file (kept about 4 hours). Supports device presets, full-page capture, a CSS selector, dark mode, and blocking ads and cookie banners. Fails for private or internal addresses. Each render counts against the account's plan.

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_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic address of the page, like https://example.com
delayNoSeconds to wait after load
detailNopreview (default): a reduced image shown inline; full: full size, inline only when small; url_only: the link alone
deviceNoA device preset id (see list_devices), like 'iphone_15'
formatNoDefault jpeg
optionsNoAny other option of the API by name; see the API options documentation
selectorNoCSS selector: capture only that element
block_adsNo
dark_modeNo
full_pageNoCapture the whole scrolling page
wait_untilNo
image_qualityNo
viewport_widthNo
viewport_heightNo
block_cookie_bannersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, open-world, idempotent, non-destructive safety profile, so the description only needs to add what they don't. It does: artifact retention (~4 hours), failure on private/internal addresses, and per-render plan consumption — all operationally relevant facts not present in structured fields.

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?

Purpose and return value are front-loaded in the first sentence, capabilities follow, and cost/failure caveats close. Every clause carries either a capability, a constraint, or a billing fact — no filler.

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 15-parameter, nested-object tool with no output schema, the description covers the two things an agent most needs and can't get elsewhere: what comes back (image plus time-limited link) and what makes calls fail or cost money. The remaining gap is the un-documented rendering parameters rather than the outcome or constraints.

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 coverage is 53% across 15 parameters, so the description must carry real weight. It names device presets, full-page capture, CSS selector, dark mode, and ad/cookie-banner blocking, which maps to about six parameters, but delay, detail, format, wait_until, image_quality, and viewport dimensions get no semantic treatment anywhere in the description.

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 and resource ('renders a public web page ... returns a screenshot') and even describes the return payload (preview image plus stored-file link). It never names a sibling such as page_to_pdf or render_html, so the agent must infer the image-vs-other-format split from the nouns alone.

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

Usage Guidelines3/5

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

Gives useful preconditions — public pages only, private/internal addresses fail, and each render is billed against the plan — which effectively tells the agent to use it sparingly. It does not say when to prefer this over page_to_pdf, page_to_markdown, or render_html, so alternative selection is left implicit.

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