Skip to main content
Glama

page_diagnostics

Read buffered console logs, network requests, downloads and dialogs for a browser tab to debug errors, inspect request payloads, and capture page issues in one call.

Instructions

Read buffered console logs, network requests, downloads and dialogs for a tab.

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": "page_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNoReturn only one section when reqId is set.
clearNo
levelNoerrors
reqIdNoInspect headers, postData, and response body for one request ID.
tabIdNo
savePathNoFile under cwd or TURBO_BROWSER_SAVE_ROOT.
urlFilterNoFilter requests/networkErrors by URL substring or regex.
dialogPolicyNo
maxBodyCharsNo
statusFilterNoerrors
includeStaticNoInclude 2xx static assets (image, font, stylesheet, media) when statusFilter=all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.1
    • changedInput schema / properties / savePath / description
      Previous value: -"Optional JSON file path relative to cwd to save diagnostics output."New value: +"File under cwd or TURBO_BROWSER_SAVE_ROOT."
  2. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and destructiveHint=false, so the safety bar is lower, and the word 'buffered' usefully signals that data is ephemeral in-memory capture. However, the description omits that the clear parameter wipes buffers, that savePath writes to disk, and that dialogPolicy can accept or dismiss dialogs (a real page mutation). These are meaningful behaviors left undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; it is efficient and readable. The risk is under-specification rather than verbosity, which is penalized elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An 11-parameter tool with nested objects, enum-driven modes, file output, and dialog actions is described in one sentence with no output schema. The definition does not give an agent enough to call it correctly without reading the schema closely and inferring semantics.

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

Parameters2/5

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

With 11 parameters and only 45% schema description coverage, the description is expected to compensate and adds nothing — no mention of reqId/part drill-down, urlFilter, statusFilter, includeStatic, or maxBodyChars. Several schema properties (tabId, clear, level, statusFilter, dialogPolicy.action) are undocumented in both places.

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?

The description uses a specific verb ('Read') and enumerates the concrete resources returned: console logs, network requests, downloads, and dialogs, scoped 'for a tab'. It is clear what the tool retrieves, but it never distinguishes itself from siblings such as network_session or inspect_compact, which likely overlap with the network/capture portion.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives despite obvious overlap with network_session, inspect_compact, and capture_page. The agent must guess which inspection tool to pick.

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