rum-analytics

get_script_performance_report

Gets a report on script performance, including average load times and impact on pages.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`daysTo`	No	Date to look to, default to yesterdays date, dd-mm-yyyy or dd-mm-yyyy hh:mm format
`domain`	Yes	Domain to get the script report for.
`rankBy`	No	The criteria for ranking pages. Options are 'Popularity' or 'Severity'. Defaults to 'Popularity'.	Popularity
`country`	No	Country to filter on. Defaults to All OR one country, in 2-letter ISO code format, eg US, GB, FR.	All
`daysBack`	No	Date to look from, default to 8 days ago, dd-mm-yyyy or dd-mm-yyyy hh:mm format
`pageSize`	No	Number of scripts to return. Defaults to 10.
`direction`	No	The sorting direction. Options are 'Worst' or 'Best'. Defaults to 'Worst'.	Worst
`pageGroup`	No	Filter by page group/category name. Defaults to All.	All
`deviceType`	No	Filter by device type: All, Desktop, Mobile, Other.	All
`pageNumber`	No	Page number for pagination. Defaults to 1.
`scriptType`	No	Filter by script type: All, Internal, or ThirdParty. Defaults to All.	All
`searchText`	No	Optional text to search for in script URL or vendor name.
`outputMaxLength`	No	The maximum number of characters for the output. Defaults to 5000
`statisticMeasure`	No	Statistical measure: P50, P75, P90, Average. Defaults to P75.	P75

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedApr 14, 2026
- changedInput schema / properties / searchText / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
First observedFeb 23, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'gets a report' without disclosing behavioral traits like read-only nature, data freshness, pagination behavior, or potential performance impact. The description is insufficient for a tool with 14 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence of 16 words; it is concise but lacks structure or elaboration. While not verbose, it could provide more information without harming conciseness.

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?

The tool has 14 parameters and no output schema, yet the description omits details about pagination, filtering options, and the various dimensions (country, device type, etc.) that the parameters support. The description is incomplete for the tool's complexity.

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 all parameters are described in the schema. The description adds no additional meaning beyond 'average load times and impact on pages,' which hints at results but not parameters. Baseline 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 the verb 'Gets a report' and the resource 'script performance', with specifics like average load times and impact. It distinguishes from siblings like get_domain_performance_overview which focuses on domain-level rather than script-level performance.

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 explicit guidance on when to use this tool or when to prefer alternatives like get_cwv_element_breakdown or get_page_performance_breakdown. The description does not mention use cases, prerequisites, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All rum-analytics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?