Skip to main content
Glama
andresolbach

nodriver-mcp-server

by andresolbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List console messages

list_console_messages
Read-only

Retrieve console messages from a page with type filtering and pagination. Requires enabling console collection beforehand.

Instructions

List console output collected for the selected page.

Requires enable_console_collection first. Console capture is opt-in because it needs the CDP Runtime domain, which some sites use to detect an attached debugger; without it this returns a reminder instead of messages.

Each line is prefixed with its id and truncated to 200 characters — pass the id to get_console_message for the full text. Only the most recent 1000 messages are retained.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typesNoOnly return these console types, e.g. ["error", "warning"]. Note the value is "warning", not "warn". Omit for all types.
browserNoWhich browser to act on. Each name is an independent Chrome, created on first use. Omit for the shared default; parallel agents each need their own name.default
page_idxNo0-based page number, used together with page_size.
page_sizeNoMaximum number of messages to return. Omit to return all.
include_preserved_messagesNoAlso include messages from before the last navigation — the server keeps the previous 3 navigations. Default false: current page only.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.0
    • addedInput schema / properties / browser
      Added value: +{
+  "default": "default",
+  "description": "Which browser to act on. Each name is an independent Chrome, created on first use. Omit for the shared default; parallel agents each need their own name.",
+  "type": "string"
+}
  2. First observedv1.7.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the operation as read-only and non-destructive, but the description adds meaningful behavioral context: console capture is opt-in due to CDP Runtime debugger detection, messages are id-prefixed and truncated to 200 characters, and only the most recent 1000 messages are retained.

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 three sentences with no filler. Purpose is front-loaded, followed by the critical prerequisite/why, then the key line-format and retention constraints. Every sentence earns its place.

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?

With detailed parameter schemas and an output schema present, the description covers the remaining essential context: prerequisite setup, degraded behavior without it, truncation, and retention limits. Nothing critical is missing for an agent to call it correctly.

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%, and the schema already documents all five parameters precisely, including the 'warning' vs 'warn' distinction, browser naming, pagination, and preserved messages. The description adds return-format context but does not need to repeat parameter semantics.

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 opens with a specific verb and resource: 'List console output collected for the selected page.' It clearly distinguishes itself from the sibling get_console_message by explaining that lines are truncated and ids can be used to fetch the full text.

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 states the prerequisite 'Requires enable_console_collection first' and warns that without it the tool returns a reminder instead of messages. It also directs the agent to get_console_message when full text is needed, providing a clear path between related tools.

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