Skip to main content
Glama

Screenshot

browser_screenshot

Capture an image of the current browser page so AI agents can inspect visual state, verify layouts, or share what they see.

Instructions

Take a screenshot of the current page. Returns the image.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing beyond 'returns the image'. It does not say whether the capture is viewport-only or full-page, what image format/encoding is returned, whether it waits for rendering, or how it behaves on a blank/error page.

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 short sentences with no waste: the action is front-loaded and the return-value hint follows. For a zero-argument tool this is an appropriately sized definition with nothing redundant.

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?

For a simple tool this is close to adequate, but with no annotations and no output schema, the description is the only source of behavioral detail and omits capture scope, image format, and failure modes. Those omissions matter for an agent deciding whether the resulting image is usable.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; the baseline for a parameterless tool applies. The description correctly implies no arguments are needed.

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?

Names a specific verb and resource ('Take a screenshot of the current page'), so an agent immediately knows the operation and that it applies to the loaded page rather than a URL argument. It does not explicitly differentiate itself from the sibling browser_snapshot, which likely captures a DOM/accessibility representation, leaving the image-vs-structure distinction to inference.

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 guidance, no statement of preconditions (e.g., a page must be navigated to first), and no mention of browser_snapshot as the alternative for non-visual inspection. The usage is only implied by the verb 'screenshot'.

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