Retrieve browser console messages buffered in the current automation session to inspect logs and debug web pages. Optionally clear the buffer or target a specific page.
Read console messages buffered by this automation session.
| Name | Required | Description | Default |
|---|---|---|---|
| clear | No | ||
| pageId | No | Stable page ID; defaults to the session active page | |
| sessionId | No | Optional session ID; defaults to this MCP client active session |
Changes observed during successful MCP inspections.
v2026.8.14Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It implies a non-destructive read, but the presence of a 'clear' parameter suggests a side effect that is not disclosed. There is also no information about buffer lifecycle, message types, or whether reading consumes messages.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is concise and to the point. It conveys the core purpose without unnecessary words, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read tool, the description is minimally viable but leaves gaps: it does not explain what 'console messages' includes (e.g., logs, errors, warnings), what happens when 'clear' is set, or the return format. These gaps are notable since there is no output schema and no annotations to fall back on.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema documents pageId and sessionId with brief descriptions, but the 'clear' parameter has no description. The tool description does not compensate for this gap, leaving the semantics of the clear parameter unclear and the overall parameter guidance incomplete.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Read') and the resource ('console messages buffered by this automation session'), making it distinct from sibling tools like network_requests or page_title. It identifies both the verb and the object precisely.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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. There is no mention of exclusions, prerequisites, or situations where another tool (e.g., network_requests or evaluate) would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.