Skip to main content
Glama

webtool_debug

Debug a webpage by capturing console output, network requests, errors, and layout thrashing with custom device emulation and adjustable output limits.

Instructions

Debug a webpage by capturing console output, network requests, errors, and layout thrashing with custom device emulation. Includes advanced response size management with pagination, output limits, and compact formatting to stay within MCP token limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the webpage to debug
captureConsoleNoCapture console.log, warn, error output
captureNetworkNoCapture network requests and responses
captureErrorsNoCapture JavaScript errors and exceptions
captureLayoutThrashingNoCapture layout thrashing events (forced layout/reflow)
timeoutMsNoHow long to collect debug information in milliseconds
useProxyNoWhether to use a proxy for this request
deviceConfigNoCustom device configuration for emulation
maxConsoleEventsNoMaximum number of console events to include in the response
maxNetworkEventsNoMaximum number of network events to include in the response
maxErrorEventsNoMaximum number of error events to include in the response
maxResourceEventsNoMaximum number of resource timing events to include in the response
skipStackTracesNoSkip stack traces in layout thrashing events to reduce response size
compactFormatNoUse compact format for all sections to reduce response size
summarizeOnlyNoInclude only summary and counts without detailed event data
pageNoPage number for paginated results (starts at 1)
pageSizeNoNumber of events per page for paginated results
ignoreSSLErrorsNoWhether to ignore SSL certificate errors (default: true for development convenience)
Behavior2/5

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

No annotations provided, so the description must fully disclose behavior. It mentions capturing output and token limits but does not disclose potential side effects like webpage loading, auth requirements, or rate limits.

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 sentences efficiently front-load the core purpose and key features without redundancy or fluff.

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 18 parameters, nested objects, and no output schema, the description provides adequate overview but lacks behavioral and usage details needed for complete agent understanding.

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% with detailed parameter descriptions, so the description adds limited additional meaning beyond mentioning pagination and compact formatting.

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 tool debugs webpages by capturing console output, network requests, errors, and layout thrashing, and distinguishes itself from sibling tools with its comprehensive debugging focus and advanced response management features.

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 siblings like webtool_network_monitor or webtool_performance_test. The description only mentions what it does, not when to choose it.

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