Skip to main content
Glama

chrome_page_load_resource_hotspots

Read-onlyIdempotent

Ranks URL-bearing resource slices within a page-load window, returning timing, overlap percentage, and process details. Use after a resource summary to identify the specific slices causing slow URLs.

Instructions

Rank URL-bearing Chrome resource/request slices in a page-load/raw window. Returns slice timing, overlap_ms/pct_of_window, process/thread, URL. Use after chrome_page_load_resource_summary to drill into the concrete Renderer/NetworkService/async slice behind a slow URL. Filters: page_load_id/navigation_id/phase, raw start/end ns, min_dur_ms default 50, limit, max_string_len.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_ts_nsNoOptional raw trace timestamp upper bound in nanoseconds, exclusive. This uses the same unit as the returned `ts` column. ANDs with any page-load window.
limitNoOptional max rows to return. Defaults to 100 and is capped at 5000. Must be > 0 when set.
max_string_lenNoOptional per-string-cell character cap applied to returned rows only. Unset preserves full strings for precision; accepts both numbers and numeric strings. Must be > 0 when set.
min_dur_msNoOptional minimum resource-like slice duration in milliseconds. Defaults to 50 ms. Pass 0 to see all matching resource slices.
navigation_idNoOptional Chrome navigation id used to scope resources to one navigation phase. Matches `chrome_page_loads.navigation_id`. Mutually exclusive with `page_load_id`. If set without `phase`, defaults to `navigation_to_fcp`.
page_load_idNoOptional page-load id used to scope resources to one navigation phase. Matches `chrome_page_loads.id`. Mutually exclusive with `navigation_id`. If set without `phase`, defaults to `navigation_to_fcp`.
phaseNoOptional page-load phase window. If set without `page_load_id` or `navigation_id`, uses the latest page load in the trace. Values: navigation_to_fcp, navigation_to_load, dcl_to_fcp, fcp_to_load.
start_ts_nsNoOptional raw trace timestamp lower bound in nanoseconds. This uses the same unit as the returned `ts` column. ANDs with any page-load window.
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds that it ranks and returns specific columns, but does not contradict annotations.

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?

Three succinct sentences: purpose & output, usage context, filter list. No redundancy or filler.

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?

Describes output fields and filter parameters adequately given no output schema. Could mention default ordering or limit but overall comprehensive.

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?

With 100% schema description coverage, the description's filter summary adds minimal new meaning. Baseline 3 is appropriate.

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?

Description uses specific verb 'Rank' and clearly identifies the resource/request slices. It distinguishes from sibling by positioning itself as a drill-down after `chrome_page_load_resource_summary`.

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?

Explicitly states 'Use after chrome_page_load_resource_summary to drill into...', providing clear context for when to invoke. Lacks when-not-to-use instructions but suffices.

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/tooluse-labs/perfetto-mcp-rs'

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