purplemux-mcp

Overview Schema Source Related Servers Discussions Admin

pmux_browser_console

Retrieve the last 500 browser console entries from a specific tab, with optional filtering by console level and incremental polling using a timestamp cursor.

Instructions

Get browser console entries { tabId, entries[] } (ring buffer, last 500). since=ms is an incremental polling cursor; level filters by console level. Electron-only (503/409).

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": {
      "workspaceId": "<workspaceId>",
      "tabId": "<tabId>"
    },
    "name": "pmux_browser_console"
  }
}

Input Schema

Name	Required	Description
`level`	No	Filter by console level (e.g. error, warning, log).
`since`	No	Incremental polling cursor in ms; only entries after this ts.
`tabId`	Yes	Target tab id (from pmux_list_tabs / pmux_create_tab).
`workspaceId`	Yes	Target workspace id (from pmux_list_workspaces).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses ring buffer limit of 500, incremental polling via 'since', filtering by 'level', and platform restriction (Electron-only with error codes 503/409). This provides solid behavioral context beyond basic function.

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?

Extremely concise: two sentences front-load the purpose and key behaviors. Every word adds value, including the ring buffer note and platform restriction. No verbose or redundant content.

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 4 parameters, no output schema, and no annotations, the description provides sufficient context: return format, capacity, parameter explanations, and platform limitation. Could mention ordering or empty result behavior, but overall adequate.

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 100% of parameters with descriptions, but the description adds value by explaining 'since' as an incremental polling cursor and 'level' as filter, plus ring buffer context. This goes beyond the schema's basic type info.

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?

Clearly states it retrieves browser console entries for a tab, specifying the return format and ring buffer capacity. While distinct from sibling tools like pmux_browser_network, it does not explicitly differentiate usage, preventing a top score.

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?

Implied usage for console log retrieval and mentions platform restriction (Electron-only), but lacks explicit guidance on when to use this tool versus alternatives like pmux_browser_network or pmux_browser_eval. No exclusions provided.

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