real-browser-mcp

Overview Schema Source Related Servers Discussions Admin

browser_console

Read browser console messages (log, warn, error) to monitor JavaScript execution and debug web applications directly from your AI coding environment.

Instructions

Read console messages (log, warn, error) from the browser

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_console"
  }
}

Input Schema

Name	Required	Description	Default
`clear`	No	Clear messages after reading

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Mar 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool reads messages but doesn't describe what happens if no messages exist, whether it returns historical or real-time data, or any limitations (e.g., rate, format). The mention of 'clear' in the schema hints at side effects, but the description doesn't address this.

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, efficient sentence with no wasted words. It front-loads the core purpose ('Read console messages') and specifies details ('log, warn, error') concisely.

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 is incomplete. It doesn't explain what the tool returns (e.g., message list format, timestamps), behavioral aspects like side effects from 'clear', or integration with browser state. For a tool with potential side effects and undefined output, this is inadequate.

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 description coverage is 100%, so the schema fully documents the single parameter 'clear'. The description adds no parameter-specific information beyond what the schema provides, meeting the baseline for high coverage.

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?

The description clearly states the verb ('Read') and resource ('console messages') with specific types mentioned ('log, warn, error'). It distinguishes from siblings like browser_click or browser_navigate by focusing on console output, though it doesn't explicitly differentiate from all browser 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active browser session), exclusions, or related tools like browser_evaluate for executing code that might produce console output.

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