Skip to main content
Glama
yurii-mandzii

shadow-monitor-mcp

Search network requests

search_network

Filter captured network requests by URL, method, status, body content, duration, and other criteria to locate specific requests.

Instructions

Filter the captured network requests and return compact rows (id, time, method, status, url, duration, type, size). Combine any filters: urlContains, method, exact status or statusMin/statusMax, failed, resourceType, mimeType, bodyContains (searches request + response bodies), minDurationMs. Filters match the raw captured values; displayed urls are field-hygiened. Paginate with limit/offset. Fetch full detail with get_network_request using a row's id (string like "e_3069").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoDefault 50.
failedNoOnly failed/blocked requests.
methodNoCase-insensitive exact match, e.g. POST.
offsetNoDefault 0.
statusNoExact status code.
bundleIdNoBundle handle from load_bundle. Optional when exactly one bundle is loaded.
mimeTypeNoSubstring match on response mime type.
statusMaxNo
statusMinNo
urlContainsNo
bodyContainsNoCase-insensitive search across request/response bodies. Short numeric needles (1–4 digits, e.g. "403") use word-boundary matching to avoid UUID/hex false positives; longer text uses substring match.
resourceTypeNoe.g. xhr, fetch, script, document.
minDurationMsNo
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that filters match raw values, displayed URLs are field-hygiened, and the row id format (e.g., 'e_3069'). It doesn't mention auth needs or rate limits, but for a search tool these are reasonable omissions.

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?

The description is two sentences, front-loaded with core purpose. The second sentence lists filters compactly, but could be better structured (e.g., bullet points or grouping). Still, it's concise and informative.

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

Completeness4/5

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

Given 13 optional parameters and no output schema, the description covers return format, filter combination, pagination, and cross-reference to get_network_request. It doesn't specify default sorting or empty-result behavior, but overall it's sufficiently complete.

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

Parameters4/5

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

With schema coverage at 69%, the description adds value by summarizing filter options and providing special behavior details (e.g., word-boundary matching for bodyContains numeric needles). This goes beyond the schema's basic descriptions.

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?

The description clearly states the verb 'Filter' and the resource 'captured network requests', specifies the compact rows returned (id, time, method, status, etc.), and distinguishes from sibling tool get_network_request which fetches full detail.

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?

The description explains how to combine filters and paginate with limit/offset, and directs users to get_network_request for full details. However, it doesn't explicitly state when not to use this tool or mention alternatives like find_errors for error-focused searches.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yurii-mandzii/shadow-monitor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server