Skip to main content
Glama

console_messages

Read console output and uncaught errors from a browser tab since it opened or was last cleared, with regex filtering and error-only options to debug page issues.

Instructions

Read console output and uncaught errors captured from a tab since it was opened or last cleared.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tabId": "<tabId>"
    },
    "name": "console_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoClear the buffer after reading
limitNoMost recent N, default 100
tabIdYesTab ID, from tabs_list or tab_create
patternNoRegex filter on the message text
onlyErrorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose useful behavior: the buffer starts at tab open or last clear. It does not state that reading is non-destructive by default, that 'clear' mutates the buffer, the ordering (newest-first), or the shape of returned entries.

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?

A single front-loaded sentence that states the action and the capture scope with no redundant wording. Nothing needs trimming and nothing is buried.

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

Completeness3/5

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

Five parameters, no annotations, and no output schema, so the description should ideally hint at the return shape (message entries, levels, error objects) and confirm default non-destructive behavior. It covers scope well but leaves the result contract and the clear-semantics gap to the schema.

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 80%, with tabId, limit, pattern, and clear already documented in the schema including the tabId source ('tabs_list or tab_create'). The description adds no parameter meaning beyond that, and onlyErrors is undocumented in both places, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Read console output and uncaught errors') plus the capture scope ('since it was opened or last cleared'), which distinguishes it from network_requests or get_page_text by subject matter. It never names an alternative sibling explicitly, so it falls short of the 5 bar for differentiation.

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?

Usage is implied by the subject matter and the capture-window phrasing, so an agent can infer when this is the right tool (debugging page JS errors or log output). There is no explicit when-to-use/when-not guidance, no mention of how this relates to network_requests, and no note that reading is non-destructive unless the 'clear' flag is set.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.