Retrieve a Chrome network request by reqid, or the latest request if omitted, including headers and bodies. Use it to inspect captured traffic during debugging.
Gets a network request by reqid (the latest request if omitted). Includes headers and bodies.
| Name | Required | Description | Default |
|---|---|---|---|
| reqid | No | ||
| pageId | No | Targets a specific page by ID. Defaults to the selected page. | |
| requestFilePath | No | ||
| responseFilePath | No |
Changes observed during successful MCP inspections.
v0.4.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It does disclose return content ('Includes headers and bodies') and the omission default, which is useful, but it says nothing about side effects, permissions, or what requestFilePath/responseFilePath produce.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single tight sentence, front-loaded with the verb and resource, with the default behavior folded in. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 4-parameter tool with no annotations and no output schema, the description partially compensates via the 'headers and bodies' note, but leaves the two file-path parameters and any return shape entirely unexplained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 25% (only pageId is documented), so the description must compensate and only explains reqid and its omission default. requestFilePath and responseFilePath are opaque in both the schema and the description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Gets a network request by reqid') plus the default behavior when the id is omitted. Clear enough to act on, but it does not explicitly differentiate itself from the sibling 'list_network_requests', so an agent must infer the single-item vs collection distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The parenthetical '(the latest request if omitted)' hints at one usage case but there is no guidance on when to prefer this over 'list_network_requests' or 'get_console_message'. No prerequisites or exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.