Skip to main content
Glama

webtool_performance_trace

Analyzes webpage performance including layout thrashing, JavaScript execution, memory growth, and resource loading. Provides actionable optimization recommendations.

Instructions

Perform a detailed performance analysis with specialized modules for layout thrashing, CSS variables impact, JavaScript execution timeline, long tasks breakdown, memory and DOM growth analysis, and resource loading optimization. Provides actionable recommendations for performance improvements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the webpage to analyze
timeoutMsNoTimeout in milliseconds for the analysis
captureCPUProfileNoWhether to capture CPU profile to identify JavaScript bottlenecks
captureNetworkActivityNoWhether to capture detailed network requests and timing
captureJSProfileNoWhether to capture JavaScript execution profile
captureRenderingPerformanceNoWhether to capture rendering performance metrics (layout shifts, layer tree)
captureMemoryProfileNoWhether to capture memory usage profile
useProxyNoWhether to use a proxy for this request
ignoreSSLErrorsNoWhether to ignore SSL certificate errors (use with caution)
analyzeLayoutThrashingNoWhether to analyze layout thrashing patterns
analyzeCssVariablesNoWhether to analyze CSS variables impact
analyzeJsExecutionNoWhether to analyze JavaScript execution and its correlation with layout events
analyzeLongTasksNoWhether to analyze long tasks and their attribution
analyzeMemoryAndDomNoWhether to analyze memory usage and DOM growth
analyzeResourceLoadingNoWhether to analyze resource loading waterfall
longTaskThresholdMsNoThreshold in milliseconds for long tasks detection
layoutThrashingThresholdNoThreshold for layout thrashing detection (number of layout operations)
memoryLeakThresholdKbNoThreshold in KB/s for memory leak detection
detailLevelNoLevel of detail in the analysis outputdetailed
includeRecommendationsNoWhether to include optimization recommendations in the output
focusSelectorNoCSS selector to focus the analysis on specific DOM elements
focusTimeRangeMsNoTime range in milliseconds to focus the analysis (format: 'start-end', e.g., '0-5000')
deviceConfigNoDevice configuration for emulation
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions analysis modules and actionable recommendations but does not disclose whether the tool modifies the page (likely read-only from 'trace' in name), potential side effects, or required permissions. The behavioral profile is partially inferred but not explicit.

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 a single, moderately long sentence that covers the main modules and value proposition. It is not excessively long but lacks structured breakdown like bullet points or sectioning. It could be more front-loaded with the primary purpose.

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 complexity (23 parameters, nested objects) and no output schema, the description provides a high-level overview but omits details on output format, pagination, or error handling. It mentions 'actionable recommendations' but does not specify the structure or depth of the analysis results.

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 description coverage is 100%, so baseline is 3. The description adds an overall context but does not explain individual parameters beyond what the schema already provides. The specialization modules listed in the description correspond directly to boolean parameters already present in the schema.

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 performs detailed performance analysis and lists specific specialized modules (layout thrashing, CSS variables, etc.). It effectively distinguishes from sibling tools like 'webtool_performance_test' or 'webtool_web_vitals' by focusing on trace-level diagnostics.

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

Usage Guidelines3/5

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

The description gives a clear overview of what the tool does but does not explicitly state when to use this tool versus alternatives like 'webtool_lighthouse' or 'webtool_performance_test'. No when-not-to-use guidance is provided, though the modules imply suitability for in-depth performance debugging.

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