Skip to main content
Glama
Sign In
Browser Bridge MCP

Browser Bridge MCP

by adbarc92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_screenshot

Capture a screenshot of the visible area of a browser tab. Specify tab ID, choose PNG or JPEG format, and adjust JPEG quality as needed.

Instructions

Capture a screenshot of the visible area of a browser tab

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
tabIdNoTab ID (defaults to active tab)
formatNoImage format (default: png)
qualityNoJPEG quality (0-100, only for jpeg format)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic action, omitting details about permissions, error handling (e.g., tab not visible), return format (image data), or side effects.

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?

Single sentence with clear, front-loaded action. No wasted words; every word earns its place.

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?

Given no annotations and no output schema, the description should compensate with behavioral and usage details. It fails to explain return type, default behavior (active tab), or constraints (visible area only). Incomplete for a tool with 3 optional parameters.

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 parameter descriptions already provide meaning. The tool description adds no extra context beyond the schema, so baseline 3 is appropriate.

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 clearly states the action ('Capture a screenshot') and the target ('visible area of a browser tab'). It is specific and distinguishes from sibling tools like browser_get_content (which retrieves HTML) and browser_status (which checks tab state).

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?

No guidance on when to use this tool versus alternatives like browser_get_content for page content or browser_evaluate for JavaScript. The description lacks context about prerequisites (e.g., tab must exist) or scenarios where screenshot is inappropriate.

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