rum-analytics

get_error_issues

Gets a list of the top JavaScript error issues (grouped by fingerprint) for a domain, with event/user/session counts, source (vendor or first-party), and triage status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Filter to a single page path, e.g. /checkout. Defaults to all pages.
`party`	No	Filter by originating party: All, FirstParty, or ThirdParty. Defaults to All.	All
`daysTo`	No	Date to look to, default to today, dd-mm-yyyy or dd-mm-yyyy hh:mm format
`domain`	Yes	Domain to get error issues for.
`vendor`	No	Filter to a single vendor name (e.g. googletagmanager.com). Defaults to All.	All
`browser`	No	Browser to filter on (e.g. Chrome, Firefox). Defaults to All.	All
`country`	No	Country to filter on, 2-letter ISO code (e.g. US, GB). Defaults to All.	All
`daysBack`	No	Date to look from, default to 7 days ago, dd-mm-yyyy or dd-mm-yyyy hh:mm format
`pageSize`	No	Number of issues to return. Defaults to 10.
`deviceType`	No	Filter by device type: All, Desktop, Mobile, Other.	All
`pageNumber`	No	Page number for pagination. Defaults to 1.
`includeBots`	No	Include bot/crawler errors (excluded by default).
`statusFilter`	No	Filter by triage status: All, Open, Resolved, Ignored. Defaults to All.	All
`outputMaxLength`	No	The maximum number of characters for the output. Defaults to 5000

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It mentions output content but not side effects, authentication, rate limits, or that it is read-only. Minimal behavioral disclosure.

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?

Single sentence front-loads the key action and output. No wasted words.

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?

With 14 parameters and no output schema, description should detail result structure. Mentions counts and status but omits format (e.g., array of objects). Lacks completeness for a complex tool.

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%, so baseline is 3. Description does not add additional meaning beyond the schema's parameter descriptions.

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 clearly states it gets top JavaScript error issues grouped by fingerprint for a domain, with specific metrics (counts, source, triage status). Distinguishes from sibling tools like get_error_issue_detail and get_error_vendors.

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?

Usage context is implied (for retrieving aggregated error issues), but no explicit when-to-use vs alternatives or exclusions. Lacks guidance compared to other error tools.

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?