Skip to main content
Glama
Sign In
oh-my-mcp

oh-my-mcp

by quyansiyuanwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_get_console_logs

Capture browser console logs including errors, warnings, and info from a page. Filter by log level for targeted debugging.

Instructions

Get browser console logs.

Captures console.log, console.error, console.warn, etc. from the page.

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": {
      "session_id": "<session_id>"
    },
    "name": "browser_get_console_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesThe session ID
levelNoFilter by log level (all, error, warning, info, debug)all

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, and the description only states that it captures logs without detailing side effects (e.g., does it clear logs?), read-only nature, or any limitations. For a tool retrieving logs, more behavioral context would be beneficial.

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?

Two sentences, front-loaded with the core purpose, no extraneous words. Efficient and clear.

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?

Given the tool's low complexity and the presence of an output schema (not detailed here), the description is sufficient for most use cases. Could mention when logs might be empty, but not critical.

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?

The schema covers 100% of parameters with descriptions. The description does not add additional meaning beyond the schema; it merely restates the function. Baseline 3 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?

The description clearly states 'Get browser console logs' and specifies 'console.log, console.error, console.warn, etc. from the page.' This uniquely identifies the tool's purpose and distinguishes it from sibling tools like browser_get_network_logs.

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?

The description implies usage when console logs are needed, but provides no guidance on prerequisites (e.g., active browser session) or when not to use it. No alternatives or exclusions are mentioned.

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