Skip to main content
Glama
frsorrentino

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

read_console

Destructive

Retrieve console messages, including errors, warnings, and logs, from a browser page to debug issues. Filter by level or limit results as needed.

Instructions

Read console messages captured since page load, incl. uncaught errors and unhandled rejections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNoClear buffer after read
levelNoall merges every level in one chronological listall
limitNoMost recent; buffer 1000
formatNolines is compact; json keeps timestamps and stack traceslines
tab_idNoTarget tab; omitted = last tab navigated in this session, else the active one
sourcemapNoResolve bundle.js:line:col frames to source files through their source maps

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.1
    • addedInput schema / properties / sourcemap
      Added value: +{
+  "default": false,
+  "description": "Resolve bundle.js:line:col frames to source files through their source maps",
+  "type": "boolean"
+}
  2. Changed3 schema fields changedv1.10.0
    • addedInput schema / properties / format / description
      Added value: +"lines is compact; json keeps timestamps and stack traces"
    • addedInput schema / properties / level / description
      Added value: +"all merges every level in one chronological list"
    • addedInput schema / properties / tab_id / description
      Added value: +"Target tab; omitted = last tab navigated in this session, else the active one"
  3. First observedv1.8.0

TDQS

A3.8/5.0
Behavior3/5

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

The description does not disclose potential side effects such as clearing the buffer if the 'clear' parameter is set, but the annotation destructiveHint=true already signals possible destructive behavior. The description does not contradict the annotation, and the parameter schema covers the clearing detail, so transparency is adequate without being explicit.

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, concise sentence that conveys the core functionality without unnecessary detail. It is well-structured and easy to parse.

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

Completeness4/5

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

The description mentions what is included (uncaught errors, unhandled rejections) giving some context. Since there is no output schema, it doesn't need to describe return values. However, it could have clarified the scope (e.g., browser console only) slightly more, but overall it is complete for typical use.

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 coverage is 100% with each parameter having a description. The description does not add further meaning beyond the schema; it only restates the tool's purpose. The baseline of 3 applies because the schema already fully documents parameters.

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 tool reads console messages captured since page load, including uncaught errors and unhandled rejections. It specifies the resource (console messages) and the action (read), and is distinct from sibling tools that read page content or DOM.

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

Usage Guidelines3/5

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

The description implies when to use (when needing console output) but does not explicitly mention alternatives or when not to use. It does not reference sibling tools like read_page or get_page_info, leaving the choice to the agent's inference.

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