Skip to main content
Glama
yfe404

proxy-mcp

by yfe404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

interceptor_browser_list_console

Retrieve buffered browser console messages (log, info, warning, error, debug) to inspect runtime issues since launch.

Instructions

List console messages buffered since the browser was launched. Types: log, info, warning, error, debug, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax messages to return (default: 50, max: 500)
typesNoFilter by console message types
offsetNoOffset into results (default: 0)
target_idYesTarget ID from interceptor_browser_launch
text_filterNoFilter by text substring

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.3
    • changedInput schema / properties / target_id / description
      Previous value: -"Target ID from interceptor_browser_launch or interceptor_camoufox_launch"New value: +"Target ID from interceptor_browser_launch"
  2. Changed1 schema field changedv3.3.1
    • changedInput schema / properties / target_id / description
      Previous value: -"Target ID from interceptor_browser_launch"New value: +"Target ID from interceptor_browser_launch or interceptor_camoufox_launch"
  3. Addedv2.3.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided. Description mentions 'buffered since browser launch' but does not disclose whether reading clears the buffer, any side effects, or other behavioral traits beyond listing. Full burden falls on description; significant gaps.

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?

Single sentence plus type enumeration. Extremely concise and front-loaded with purpose. Every piece of information earns its place.

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?

Adequate for basic understanding of purpose. Missing return format details (no output schema) and no explanation of pagination or filtering behavior beyond parameter descriptions. Could be more complete given five parameters.

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 100%, and the description adds minor value by listing example console types (log, info, warning, debug) beyond schema. However, no additional semantics are provided for other parameters beyond schema descriptions.

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?

Description clearly states it lists console messages buffered since browser launch and enumerates types. Name and description align well. Among siblings like interceptor_browser_list_cookies, it distinguishes by resource (console) but does not explicitly differentiate usage.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No mention of prerequisites (e.g., needing a launched browser), when not to use, or relationship to other list tools. Usage context is only implied.

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