Skip to main content
Glama
Sign In
Browser Bridge MCP

Browser Bridge MCP

by adbarc92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_get_console

Retrieve console log entries from a browser tab to debug errors and monitor logs. Optionally clear logs after retrieval.

Instructions

Get captured console log entries from a 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_get_console"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoClear logs after retrieval (default: false)
tabIdNoTab ID (defaults to active tab)

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, the description carries full burden. It implies a read operation but does not disclose whether retrieving logs is destructive by default (the 'clear' parameter is optional). It also fails to mention if logs are only available after navigation or if the tool clears logs automatically before returning.

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 sentence with no unnecessary words. It is front-loaded with the core action and resource, making it easy to scan.

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 has no output schema, so the description should explain what the agent receives (e.g., array of log entries, each with message, level, timestamp). It does not. Also, it does not clarify behavior when no logs exist or when the tab is closed.

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?

Both parameters have descriptions in the schema, so baseline is 3. The description adds no extra meaning beyond the parameter names and schema; e.g., it does not clarify what 'console log entries' includes (errors, warnings, logs) or the format of the returned data.

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 ('Get') and the resource ('captured console log entries') with context ('from a tab'). Among the sibling tools (e.g., browser_get_content, browser_evaluate), none duplicate this purpose, making it distinct and specific.

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 is provided on when to use this tool versus alternatives, such as browser_evaluate for runtime expressions or browser_get_content for page source. The description does not mention prerequisites like enabling console capture or tab activity.

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