Skip to main content
Glama

list_network_requests

Read-only

Retrieve network requests from a Chrome browser page to analyze performance, debug issues, or inspect resources like scripts and images.

Instructions

List all requests for the currently selected page since the last navigation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageSizeNoMaximum number of requests to return. When omitted, returns all requests.
pageIdxNoPage number to return (0-based). When omitted, returns the first page.
resourceTypesNoFilter requests to only return requests of the specified resource types. When omitted or empty, returns all requests.

Implementation Reference

  • The handler function that sets the response to include network requests for the selected page, applying pagination (pageSize, pageIdx) and resource type filtering.
    handler: async (request, response) => {
      response.setIncludeNetworkRequests(true, {
        pageSize: request.params.pageSize,
        pageIdx: request.params.pageIdx,
        resourceTypes: request.params.resourceTypes,
      });
    },
  • Zod schema defining optional input parameters for pagination and filtering network requests.
    schema: {
      pageSize: z
        .number()
        .int()
        .positive()
        .optional()
        .describe(
          'Maximum number of requests to return. When omitted, returns all requests.',
        ),
      pageIdx: z
        .number()
        .int()
        .min(0)
        .optional()
        .describe(
          'Page number to return (0-based). When omitted, returns the first page.',
        ),
      resourceTypes: z
        .array(z.enum(FILTERABLE_RESOURCE_TYPES))
        .optional()
        .describe(
          'Filter requests to only return requests of the specified resource types. When omitted or empty, returns all requests.',
        ),
    },
  • src/main.ts:307-320 (registration)
    Collects tool definitions from all tool modules, including networkTools which exports listNetworkRequests, and registers each with the MCP server via registerTool.
    const tools = [
      ...Object.values(consoleTools),
      ...Object.values(emulationTools),
      ...Object.values(inputTools),
      ...Object.values(networkTools),
      ...Object.values(pagesTools),
      ...Object.values(performanceTools),
      ...Object.values(screenshotTools),
      ...Object.values(scriptTools),
      ...Object.values(snapshotTools),
    ];
    for (const tool of tools) {
      registerTool(tool as unknown as ToolDefinition);
    }
  • Defines the array of filterable Puppeteer ResourceType enums used in the schema for resourceTypes parameter.
    const FILTERABLE_RESOURCE_TYPES: readonly [ResourceType, ...ResourceType[]] = [
      'document',
      'stylesheet',
      'image',
      'media',
      'font',
      'script',
      'texttrack',
      'xhr',
      'fetch',
      'prefetch',
      'eventsource',
      'websocket',
      'manifest',
      'signedexchange',
      'ping',
      'cspviolationreport',
      'preflight',
      'fedcm',
      'other',
    ];
Behavior3/5

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

The annotations provide readOnlyHint=true, indicating a safe read operation. The description adds context about the temporal scope ('since the last navigation'), which is useful behavioral information not covered by annotations. However, it doesn't disclose other traits like pagination behavior (implied by parameters but not described), rate limits, or error conditions.

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?

The description is a single, clear sentence that efficiently conveys the core purpose without unnecessary words. It's front-loaded with the main action and scope, making it easy to parse and understand quickly.

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?

Given the tool's moderate complexity (list operation with filtering/pagination), the description covers the basic purpose and scope. However, with no output schema and annotations only indicating read-only, it lacks details on return format (e.g., structure of listed requests) and could benefit from more behavioral context for a network-related tool.

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?

The input schema has 100% description coverage, clearly documenting all three parameters (pageSize, pageIdx, resourceTypes) with their purposes and defaults. The description doesn't add any semantic details beyond what's in the schema, so it meets the baseline of 3 for high schema coverage without extra value.

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?

The description clearly states the action ('List all requests') and the scope ('for the currently selected page since the last navigation'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'get_network_request' (singular vs. plural) or 'list_console_messages', which might handle similar data but for different resources.

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?

The description provides some context ('since the last navigation') but lacks explicit guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_network_request' for single requests or 'list_console_messages' for other page data, nor does it specify prerequisites (e.g., requires a selected page).

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/SHAY5555-gif/chrome-devtools-mcp'

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