Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

screenshot

Capture a browser tab as a base64-encoded PNG image for visual inspection or sharing.

Instructions

Take screenshot (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": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 mostly does not meet it. It discloses the return encoding (base64 PNG), which is genuinely useful, but says nothing about scope (viewport vs full page), what happens on a background or missing tab, or whether the call requires an active connection.

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?

One short clause with zero wasted words, and the return format is conveniently front-loaded in parentheses. It is efficient, though brevity here edges toward under-specification rather than disciplined conciseness.

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 low-complexity browser tool this is close to adequate, but with no annotations, no output schema, an undocumented optional parameter, and no statement of capture scope or required session state, an agent cannot call it confidently without trial and error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter tabId has 0% schema description coverage and is never mentioned in the description. With an optional parameter, the critical unknown is the default target when tabId is omitted — presumably the active tab — and the description leaves that entirely unstated.

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 ("Take screenshot") so the agent knows the core action, and adds the return format. It does not differentiate from the sibling "snapshot", which an agent could plausibly confuse with a capture operation, so it falls short of a 5.

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 at all: no statement of when a screenshot is preferable to snapshot/evaluate, no prerequirements such as a connected session or loaded page. The agent must infer usage entirely from the name.

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