Skip to main content
Glama
pluginslab

devtools-fleet-mcp

by pluginslab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_console_messages

Read-only

List all console messages for the target page since the last navigation.

Instructions

List all console messages for the target page since the last navigation.

Input Schema

NameRequiredDescriptionDefault
typesNoFilter messages to only return messages of the specified resource types. When omitted or empty, returns all messages.
pageIdYesTargets a specific page by ID.
pageIdxNoPage number to return (0-based). When omitted, returns the first page. Ignored unless pageSize is set.
pageSizeNoMaximum number of messages to return. When omitted, returns all messages.
serviceWorkerIdNoFilter messages by the service worker ID shown by list_pages (sw-N).
includeStackTracesNoSet to true to include the stack trace for each message when available. Increases the response size.
includePreservedMessagesNoSet to true to return the preserved messages over the last 3 navigations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • changedInput schema / additionalProperties
      Previous value: -{}New value: +false
    • changedInput schema / properties / pageIdx / description
      Previous value: -"Page number to return (0-based). When omitted, returns the first page."New value: +"Page number to return (0-based). When omitted, returns the first page. Ignored unless pageSize is set."
    • changedInput schema / properties / serviceWorkerId / description
      Previous value: -"Filter messages to only return messages of the specified service worker."New value: +"Filter messages by the service worker ID shown by list_pages (sw-N)."
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds the meaningful constraint that only messages since the last navigation are returned (with includePreservedMessages extending to three navigations left to the schema), but says nothing about ordering, volume, or output shape.

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?

One sentence, front-loaded with the action and resource, with zero filler. Nothing is padded or repeated from the schema.

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?

For a read-only listing tool with a fully documented schema, the description is adequate but leaves out the two things an agent most needs: how this differs from get_console_message, and the fact that preserved messages require an opt-in flag to be visible.

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 description coverage is 100%, so all seven parameters are self-documenting, including the filter, pagination, and preserved-message flags. The description adds no parameter insight beyond the schema, which is the baseline case.

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?

States a specific verb and resource ('List all console messages') plus a scope ('for the target page since the last navigation'). It does not distinguish itself from the sibling get_console_message, which fetches a single message, so an agent must infer the list-vs-single split.

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 explicit when-to-use guidance and no mention of the obvious alternative, get_console_message, or of when a bulk listing is preferable. The scope phrase hints at coverage but gives no selection criteria.

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