Skip to main content
Glama

webtool_network_monitor

Analyze network activity and resource loading performance for any webpage to identify bottlenecks and optimization opportunities.

Instructions

Analyze network activity and resource loading performance. Provides detailed insights into network requests, timing, and optimization opportunities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the webpage to analyze
timeoutMsNoTimeout in milliseconds for the analysis
waitAfterLoadMsNoAdditional time to wait after page load to capture more requests
useProxyNoWhether to use a proxy for this request
ignoreSSLErrorsNoWhether to ignore SSL certificate errors (use with caution)
includeThirdPartyNoWhether to include third-party requests in the analysis
disableCacheNoWhether to disable browser cache for the analysis
captureHeadersNoWhether to capture request and response headers
captureContentNoWhether to capture request and response content
captureTimingsNoWhether to capture detailed timing information
filterByTypeNoFilter requests by resource type (e.g., 'document', 'stylesheet', 'script', 'image', 'font', 'media', 'json', 'text')
filterByDomainNoFilter requests by domain (e.g., 'example.com')
sortByNoSort requests by a specific propertystartTime
networkConditionNameNoPredefined network condition to emulate (e.g., 'Slow 3G', 'Fast 3G', '4G', 'WiFi', 'Fiber')
networkConditionNoCustom network condition configuration
deviceNameNoPredefined device to emulate (e.g., 'Pixel 7', 'iPhone 14')
deviceConfigNoCustom device configuration for emulation
maxRequestsNoMaximum number of requests to include in the response (to limit response size)
summarizeOnlyNoWhether to include only summary and recommendations without detailed request data (to reduce response size)
pageNoPage number for paginated results (starts at 1)
pageSizeNoNumber of requests per page for paginated results
includeRecommendationsNoWhether to include optimization recommendations in the output
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only describes it as an analysis tool with no mention of side effects, required permissions, or whether it modifies state. It implies a read-only operation but does not explicitly confirm safety.

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?

Two sentences, concise, and front-loaded with the main action. However, it lacks structure such as bullet points or sectioning, but is still efficient.

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

Completeness2/5

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

Given 22 parameters, nested objects, and no output schema, the description is insufficient. It does not explain how results are returned, pagination, or output format. For a complex tool, more context is needed.

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%, and each parameter has a description in the schema. The tool description adds no extra meaning beyond the schema. Baseline of 3 is appropriate.

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 it analyzes network activity and resource loading performance. It provides insights into network requests, timing, and optimization. However, it does not differentiate itself from sibling tools like webtool_performance_test or webtool_lighthouse, which also involve performance analysis.

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?

No guidance on when to use this tool versus alternatives. It does not specify prerequisites, contexts where it is appropriate, or when to avoid using it. Sibling tools are not mentioned or contrasted.

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/misterboe/webtools-mcp-server'

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