Skip to main content
Glama
Sign In
devtools-fleet-mcp

devtools-fleet-mcp

by pluginslab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_network_requests

Read-only

Lists the most recent requests for the target page since the last navigation.

Instructions

Lists the most recent requests for the target page since the last navigation.

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": {
      "pageId": "<pageId>"
    },
    "name": "list_network_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 requests to return. When omitted, returns all requests.
resourceTypesNoFilter requests to only return requests of the specified resource types. When omitted or empty, returns all requests.
includePreservedRequestsNoSet to true to return the preserved requests 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 / resourceTypes / items / enum
      Previous value: -[
-  "document",
-  "stylesheet",
-  "image",
-  "media",
-  "font",
-  "script",
-  "texttrack",
-  "xhr",
-  "fetch",
-  "prefetch",
-  "eventsource",
-  "websocket",
-  "manifest",
-  "signedexchange",
-  "ping",
-  "cspviolationreport",
-  "preflight",
-  "fedcm",
-  "other"
-]New value: +[
+  "document",
+  "stylesheet",
+  "image",
+  "media",
+  "font",
+  "script",
+  "texttrack",
+  "xhr",
+  "fetch",
+  "prefetch",
+  "eventsource",
+  "manifest",
+  "signedexchange",
+  "ping",
+  "cspviolationreport",
+  "preflight",
+  "fedcm",
+  "other"
+]
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

readOnlyHint=true already signals a safe read, and the description adds genuinely useful behavioral scoping: results are limited to the window since the last navigation. That window is the key non-obvious trait (the schema's includePreservedRequests only indirectly reveals the 3-navigation alternative), though ordering guarantees and response shape remain unstated.

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 no filler; the scope qualifier arrives immediately after the verb. It is efficient, though slightly thin given five parameters and no output 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?

With full schema coverage and a readOnly annotation, a short description can suffice, but for a 5-parameter list tool with no output schema the description says nothing about result shape, ordering, or whether the list is a point-in-time snapshot. It is adequate but leaves real questions for the agent to discover at call time.

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 pagination, filtering by resourceTypes, and preserved-request behavior are already fully documented. The description only echoes the page targeting and implies recency ordering ('most recent'), adding little beyond the structured field text.

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?

Specific verb (Lists) plus resource (network requests) scoped to a target page, which cleanly separates it from the single-item sibling get_network_request. It doesn't name that sibling explicitly, so differentiation is inferred from the singular/plural naming rather than stated.

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?

Usage is only implied by the phrase 'target page since the last navigation' – there is no statement of when to prefer this over get_network_request, nor any prerequisite such as the page needing to be loaded or selected first. An agent can guess the intent but gets no routing guidance.

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