action1-mcp-server

Get report errors

action1_list_report_errors

Read-onlyIdempotent

Retrieves errors for a specified report, letting you filter, sort, and paginate report error records for review and troubleshooting.

Instructions

Get report errors. Returns report errors for the specified report. Perm: view_reports.

Input Schema

Name	Required	Description
`from`	No	Provide the number of the first record to be returned.
`limit`	No	Set the maximum number of items to be returned (the page size).
`cursor`	No	next_cursor of the previous call; takes precedence over from.
`filter`	No	Provide a case-insensitive substring to filter and narrow down returned results (i.e., if...
`org_id`	No	Org UUID.
`sortby`	No	Define the sorting order by a certain field.
`verbose`	No	Skip per-item compactor.
`report_id`	Yes	Provide a specific report ID.
`auto_paginate`	No	Walk pages until limit or the size budget; then continue with next_cursor.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`items`	Yes
`total`	No
`has_more`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.6.0Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / auto_paginate / description

Previous value: -"Walk all pages."New value: +"Walk pages until limit or the size budget; then continue with next_cursor."

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor."New value: +"next_cursor of the previous call; takes precedence over from."

addedInput schema / properties / from / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / from / minimum
```
Added value: +0
```
addedInput schema / properties / limit / maximum
```
Added value: +50000
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

addedOutput schema / properties / items / items / properties

Added value: +{
+  "description": {},
+  "endpoint_id": {},
+  "endpoint_name": {},
+  "id": {},
+  "self": {},
+  "timestamp": {},
+  "type": {}
+}

First observedv0.5.0Jun 27, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds the required permission scope (view_reports), which is real information beyond the annotations. It says nothing about result volume, pagination behavior, or how errors relate to the parent report's rows.

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?

Very short, but the opening sentence merely restates the title and the second restates it again with scope. The only non-redundant content is the permission clause. Front-loading is fine but roughly half the text is 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?

For a 10-parameter read-only tool with a fully documented schema and an output schema, the description covers the essentials: target resource, scoping to one report, and the required permission. The main gap is not distinguishing error records from report data records, which the agent would have to infer.

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%, including documented meaning for from/limit/cursor/filter/auto_paginate, so the baseline is 3. The description only reinforces that report_id identifies the target report and adds nothing beyond the schema (e.g., no hint about what 'error' records contain or how filter applies to them).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb+resource ('Get report errors') and scopes it to a specific report, but the first and second sentences are near-duplicates, adding no extra precision. It gives no distinction from adjacent siblings such as action1_list_report_data or action1_list_installed_software_errors, so the agent cannot tell from the text which error-listing tool it needs.

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?

'Perm: view_reports' tells the agent a prerequisite, which is genuinely useful context. However, there is no guidance on when to use this versus the other report-related tools, and no stated exclusions or alternatives. Usage is only implied by the resource name.

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

Deploy Server