Skip to main content
Glama
Sign In
mcp-browser-automation

mcp-browser-automation

by ritesh-jain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

capture_screenshot

Capture a screenshot of the current page in a browser session, providing a visual record of the page's state for inspection or documentation.

Instructions

Take a screenshot of the current page

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

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name for the screenshot file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the action, omitting important details such as whether it captures the viewport or full page, whether it returns a file path or base64, and whether it waits for page load. This is inadequate for a tool with no annotation support.

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?

The description is a single concise sentence that is front-loaded and contains no fluff. It earns its place by clearly stating the core action.

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?

The tool is simple with one optional parameter and no output schema, but the description still leaves critical gaps: it does not explain what the tool returns, whether the screenshot is saved to a file, or what behavior to expect. For a tool without annotations, this is insufficient.

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?

The only parameter, 'name', is fully described in the input schema as 'Optional name for the screenshot file' (100% schema coverage). The description adds no additional meaning, but the baseline of 3 is appropriate since the schema already covers the parameter semantics.

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 'Take a screenshot of the current page' uses a specific verb ('take') and a clear resource ('screenshot of the current page'). It clearly distinguishes this tool from siblings like navigate, get_console_logs, or execute_js, which serve different purposes.

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?

The intended use is implied: use this when a visual capture of the current page is needed. However, there is no explicit guidance on when not to use it or how it compares to alternatives, leaving the agent to infer the context from the tool's name.

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