Skip to main content
Glama
Gwakko

agent-in-browser

by Gwakko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

console_messages

Read-only

Lists browser console output captured since attach so you can debug a page after an action fails or confirm no errors. Filter by level or pattern, and clear between steps.

Instructions

Read-only: list browser console output (console.log/warn/error and uncaught exceptions) captured since agent-in-browser attached to the tab, one line per entry as [time] LEVEL text, oldest first. Use it to debug a page after an action fails or to confirm no errors. Capture starts on attach, so messages printed during an earlier page load are missed: navigate with action=reload first. Use clear to reset between steps. For HTTP traffic use network_requests.

Input Schema

NameRequiredDescriptionDefault
tabNoTab id from tabs_list. Defaults to the current tab.
clearNoEmpty the console buffer after reading so the next call only shows new messages.
levelNoOnly entries of this level (error also includes uncaught exceptions).
limitNoReturn only the last N matching entries (default 100).
patternNoRegular expression the message text must match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.2
    • changedInput schema / properties / clear / description
      Previous value: -"Clear the buffer after reading."New value: +"Empty the console buffer after reading so the next call only shows new messages."
    • changedInput schema / properties / level / description
      Previous value: -"Only this level (error includes uncaught exceptions)."New value: +"Only entries of this level (error also includes uncaught exceptions)."
    • changedInput schema / properties / limit / description
      Previous value: -"Last N entries (default 100)."New value: +"Return only the last N matching entries (default 100)."
    • changedInput schema / properties / pattern / description
      Previous value: -"Regex the text must match."New value: +"Regular expression the message text must match."
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only annotation, the description discloses important behavioral traits: capture begins when the agent attaches, earlier page-load messages are missed, output is one line per entry in `[time] LEVEL text` form oldest first, and clear empties the buffer.

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 front-loaded with purpose, then usage, caveats, and alternatives. Every sentence contributes useful selection or invocation guidance with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only console-listing tool with full schema coverage and no output schema, the description covers purpose, capture behavior, output format, usage guidance, reset behavior, and the relevant alternative.

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 tab, clear, level, limit, and pattern are already documented in the schema. The description adds context around clear and error-level inclusion of uncaught exceptions, but most parameter meaning is carried by the schema.

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 states a specific verb and resource: list browser console output including console.log/warn/error and uncaught exceptions. It also distinguishes the tool from network_requests, making selection clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use the tool (debug after an action fails, confirm no errors), gives a prerequisite (navigate with action=reload first because capture starts on attach), explains how to reset via clear, and names an alternative for HTTP traffic.

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