Skip to main content
Glama

Console logs

browser_get_console_logs

Retrieve console messages and page errors collected since the previous call to diagnose browser-side issues after navigation or interaction.

Instructions

Get console messages and page errors collected since the last call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_get_console_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden, and it does disclose the key trait: the result is incremental, covering only what was collected since the previous invocation. That implies the read is cursor-like and that earlier messages are not repeated, which is genuinely useful. It does not say whether the buffer is cleared, whether the call blocks or waits for new entries, or whether messages and errors are interleaved or grouped.

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 twelve-word sentence with no filler, and the incremental-scope qualifier is placed at the end where it reads as a constraint on the result rather than a buried caveat. Nothing could be removed without losing meaning.

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?

There is no output schema, so the return shape falls to the description, which never says whether the result is a list of strings, structured entries with levels and source URLs, or a single blob. For a zero-parameter read tool the description is serviceable, but the shape of console entries and whether the buffer is consumed are left unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter detail is missing because no parameters exist.

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?

States a specific verb ("Get") and two specific resources ("console messages and page errors"), which is far more precise than a generic "get logs" restatement. It is clearly distinct from every sibling, none of which deal with log/error retrieval, though it never names an alternative explicitly.

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?

"since the last call" implies the intended workflow — call this after taking actions to inspect what the page emitted — but that is inference rather than stated guidance. There is no explicit when-to-use, when-not-to-use, or pointer to a related tool for a different view of the same data.

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