Skip to main content
Glama
jkresearch8

@domscout/mcp

by jkresearch8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Screenshot a page

domscout_capture_screenshot

Capture a rendered webpage screenshot to verify layout, styling, or visual state. Supports viewport, full-page, element, and format options, returning the image directly.

Instructions

Costs 1 credit for a viewport PNG/JPEG/WebP; +1 for fullPage, +1 for PDF. Returns the image itself. Use this when you need to see layout, styling, or a visual state — for reading text, domscout_extract_markdown is cheaper and more useful.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe page to load. Must be http(s) and publicly reachable. Credentials in the URL (https://user:pass@host) are rejected; these tools capture as an anonymous visitor, so use the REST API directly if the page needs authentication.
delayNoExtra milliseconds to wait after load.
widthNoViewport width in CSS pixels.
formatNoPDF requires a Pro plan or above.png
heightNoViewport height in CSS pixels.
qualityNoJPEG/WebP quality.
fullPageNoCapture the whole scrollable page. Requires Pro or above. Adds 1 credit.
selectorNoCapture only this element.
devicePresetNoPreset viewport and device characteristics. Overrides width/height when set.
hideSelectorsNoElements to hide before capturing, e.g. cookie banners.
waitForSelectorNoWait for this CSS selector to appear before capturing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly discloses the credit cost, the extra cost for fullPage and PDF, and the fact that the response is the image itself. It does not mention anonymous-visitor auth or failure behavior, but those are already captured in the URL parameter description.

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?

Two sentences with no filler: cost and return type come first, followed by a clear usage recommendation. Every clause contributes decision-relevant information.

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?

Together with the fully documented 11-parameter schema, the description gives an agent enough context to invoke the tool correctly: cost, output, and when to prefer a sibling. It omits only minor execution-time details such as network error handling or image size limits, which are not essential for tool selection.

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. The description adds value by explaining the credit implications of fullPage and PDF, which the schema does not cover. It does not need to restate parameter details already fully documented 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?

The description states a specific verb and resource: capturing a viewport screenshot as PNG/JPEG/WebP, plus fullPage and PDF variants. It also distinguishes the tool from domscout_extract_markdown, so an agent can tell them apart without opening schemas.

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?

It explicitly says to use this tool when layout, styling, or visual state is needed, and it names domscout_extract_markdown as cheaper and more useful for reading text. This is a concrete when-to-use/when-not-to-use rule with a named alternative.

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

Deploy Server

Other Tools