Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

console_messages

Retrieve captured browser console output from a page to debug errors, warnings, and logs, with an option to clear stored messages after reading.

Instructions

Get captured console messages from the page

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

Input Schema

NameRequiredDescriptionDefault
clearNoClear messages after retrieving (default false)
tabIdNoTab ID (optional)

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?

With no annotations supplied, the description carries the full behavioral burden and does not meet it. It never discloses that messages are buffered/captured over the page session, that the 'clear' flag has a destructive side effect on that buffer, or whether the read is scoped to a tab; these are exactly the traits an agent needs for a state-touching tool.

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, front-loaded with verb and resource, with no filler or redundancy. It is efficient, though its brevity is part of why behavioral gaps remain rather than a virtue of structure.

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 tool with no annotations and no output schema, the description should at least sketch the return shape (a list of console entries with level/message), buffering lifetime, and the destructive nature of 'clear'. None of that is present, leaving the agent to guess at behavior and results from the schema alone.

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 both 'clear' and 'tabId' are already documented in the schema, which sets the baseline at 3. The description adds only the notion that messages were 'captured', which loosely implies accumulation, but clarifies nothing about the parameters themselves or about what clearing affects.

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 ('Get captured console messages') with the scope 'from the page', which is enough to tell it apart from data-retrieval siblings like network_requests or get_page_content by resource type. It stops short of explicitly naming or contrasting those siblings, so it is clear but not fully differentiated.

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 offers no when-to-use guidance, no prerequisites (e.g. that the page must have been loaded and messages buffered), and no mention of alternatives such as network_requests for network activity. The agent must infer usage entirely from the name and resource.

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