nodriver-mcp-server

Overview Schema Source Related Servers Discussions Admin

Search captured bodies

search_bodies

Read-only

Trace where a value appears in captured HTTP traffic: find the first response that contained it and the later requests that sent it back.

Instructions

Find where a value shows up in the traffic capture_bodies recorded — in which response it first arrived, and which later requests sent it back.

The usual question when following data through an app: where did this ID, token or price come from, and where does it go next. Results are in capture order, so the first hit is the first response that carried it; POST data and URLs from capture.jsonl are searched too, as the "sent" side.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Text to look for, or a regular expression with regex=true.
`regex`	No	Treat query as a Python regular expression.
`browser`	No	Which browser to act on. Each name is an independent Chrome, created on first use. Omit for the shared default; parallel agents each need their own name.	default
`directory`	No	A capture_bodies folder to search. Empty uses the running capture, or the most recent one.
`max_results`	No	Stop after this many matches.
`case_sensitive`	No	Match case exactly. Default false.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.5.0Sep 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Adds meaningful behavior beyond the readOnlyHint: results are in capture order, the first hit is the first response that carried the value, and POST data and URLs from capture.jsonl are included as the 'sent' side. This is useful context not present in annotations and does not contradict them.

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?

Two short paragraphs with the core semantics front-loaded in the first sentence. The 'usual question' sentence earns its place by clarifying the intended use case; there is no filler or repetition.

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

Completeness5/5

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

With a complete input schema, an output schema, and annotations already covering the read-only safety profile, the description supplies the missing behavioral context: ordering, 'sent' side coverage, and the kind of value being searched. Nothing needed for correct invocation is missing.

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 coverage is 100%, so the input schema already documents all six parameters with meaningful descriptions. The tool description adds no parameter-level detail, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('find') and resource ('capture_bodies'), then gives precise semantics: which response first carried a value and which later requests sent it back. This clearly distinguishes it from sibling tools focused on live network requests or other browser actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly frames the intended use case: following an ID, token, or price through an app to see where it originated and where it went next. It does not explicitly name sibling alternatives or state 'when not to use', but the context is unambiguous.

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

Deploy Server