Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

take_screenshot

Capture screenshots of the current page, full scrollable page, or a specific element and return them as base64 images for visual inspection or documentation.

Instructions

Capture a screenshot of the page (returns base64 PNG)

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

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
formatNoImage format (default png)
qualityNoJPEG quality 0-100 (if format is jpeg)
fullPageNoCapture full scrollable page (default false)
selectorNoCSS selector to screenshot a specific element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/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 burden and does little: it notes the output is base64 PNG, which is genuinely useful, but says nothing about whether a tab must be selected first, payload size/timeouts on large or full-page captures, or side effects. For a read-style capture tool this is thin rather than misleading.

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?

A single short sentence with the return format front-loaded in parentheses and zero filler. It is efficient, though the brevity reads as under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five optional parameters, no output schema, and no annotations, the description covers the action and return encoding but omits tab-state prerequisites and behavior for element-scoped vs full-page captures. Adequate to call the tool, not sufficient to call it well in edge cases.

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 100%, so the schema already documents tabId, format, quality, fullPage, and selector, making 3 the baseline. The description adds only the return encoding, and its '(returns base64 PNG)' phrasing slightly obscures that the format parameter permits jpeg and webp.

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 ('Capture a screenshot of the page') plus the return encoding, so the core action is unambiguous. It does not distinguish itself from nearby siblings like take_snapshot or print_to_pdf, which could look like screenshot-adjacent tools.

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 guidance on when to use this instead of take_snapshot, get_page_content, or print_to_pdf, and no prerequisites such as needing an open/active tab. The agent must infer the choice from tool names alone.

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