Skip to main content
Glama
frsorrentino

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

read_console

Destructive

Retrieve console messages captured since page load, including uncaught errors and unhandled rejections, to debug browser issues; use clear to delete returned logs or since cursor for newer entries.

Instructions

Read console messages captured since page load, incl. uncaught errors and unhandled rejections. clear deletes the messages it returns, hence not read-only; since=cursor reads only newer ones without deleting, and failed requests are in monitor_network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNoClear buffer after read
levelNoall merges every level in one chronological listall
limitNoMost recent; buffer 1000
sinceNocursor from the previous read: only newer entries, nothing deleted
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.28.0
    • addedInput schema / properties / since
      Added value: +{
+  "description": "cursor from the previous read: only newer entries, nothing deleted",
+  "type": "string"
+}
  2. 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"
+}
  3. 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"
  4. First observedv1.8.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the crucial detail of WHAT is destroyed (the messages it returns) and offers the non-destructive since=cursor path. That is meaningful context beyond the annotations, though it says nothing about buffer limits or rate behavior (partly covered by the schema).

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?

Three tightly packed sentences with zero filler. The core purpose is front-loaded, and the destructive caveat and alternative are stated immediately after without redundancy.

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?

For a 7-parameter tool with no output schema, the description covers purpose, destructive semantics, the non-destructive alternative, and sibling routing. It leaves return-value shape implicit, but the format parameter and lack of an output schema make that acceptable.

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 all seven parameters are already documented in the schema, including the clear and since semantics the description restates. The description adds only marginal cross-parameter meaning, so the baseline of 3 for fully-covered schemas is appropriate.

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?

States a specific verb (Read) and resource (console messages captured since page load), and scopes it further by naming uncaught errors and unhandled rejections. It also distinguishes itself from the sibling monitor_network for failed requests, so an agent can route correctly without opening another schema.

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?

Explicitly contrasts the two read modes: clear deletes what it returns (destructive), while since=cursor reads only newer entries without deleting. It also routes a specific need (failed requests) to monitor_network, giving a clear when-not to use this tool.

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