Skip to main content
Glama

get_console_logs

Read-only

Retrieve browser console logs with filtering by type, text search, and time range. Choose grouped output to see deduplicated lines with counts or raw chronological format.

Instructions

[may return preview+token] Retrieve console logs with filtering and token‑efficient output. Defaults: since='last-interaction', limit=20, format='grouped'. Grouped output deduplicates identical lines and shows counts. Use format='raw' for chronological, ungrouped lines. Large outputs return a preview and a one-time token to fetch the full payload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoType filter (all, error, warning, log, info, debug, exception). Note: 'error' also includes 'exception' entries for convenience.
searchNoText to search for in logs (handles text with square brackets)
limitNoMaximum entries to return (groups when grouped, lines when raw). Default: 20
sinceNoFilter logs since a specific event: 'last-call' (since last get_console_logs call), 'last-navigation' (since last page navigation), or 'last-interaction' (since last user interaction like click, fill, etc.). Default: 'last-interaction'
formatNoOutput format: 'grouped' (default, deduped with counts) or 'raw' (chronological, ungrouped)
Behavior5/5

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

Discloses key behaviors: token mechanism for large outputs, deduplication in grouped mode, and default parameter values. Consistent with 'readOnlyHint: true' annotation, and adds behavioral context beyond annotations.

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?

Four concise sentences, front-loaded with key information (preview+token). Each sentence adds essential detail without redundancy. No fluff or unnecessary words.

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?

Despite lacking an output schema, the description fully explains return behavior (preview+token, grouped vs raw), defaults, and parameter effects. An agent can effectively use this tool with the provided information.

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?

Schema covers all 5 parameters with descriptions (100% coverage). The description adds value by stating defaults for 'limit', 'since', and 'format', and clarifying the meaning of 'since' values (e.g., 'last-interaction'). This goes beyond the schema's parameter descriptions.

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 'Retrieve console logs with filtering and token-efficient output', specifying the verb 'Retrieve', the resource 'console logs', and key features. It distinguishes from siblings like 'clear_console_logs' and other DOM/network tools.

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

Usage Guidelines4/5

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

Provides clear usage context: explains the two formats ('grouped' vs 'raw'), the 'since' options, and defaults. Does not explicitly mention when not to use this tool or compare to alternatives, but covers enough guidance for appropriate use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/antonzherdev/mcp-web-inspector'

If you have feedback or need assistance with the MCP directory API, please join our Discord server