action1-mcp-server

Get report rows

action1_list_report_data

Read-onlyIdempotent

Fetch paginated report rows with filters, sorting, and optional details to inspect Action1 report data.

Instructions

Get report rows. Gets data organized by report rows. Use parameters to filter out returned results. 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.
`details`	No	Specify 'yes' to expand the details. This parameter is supported only for Summary reports.
`verbose`	No	Skip per-item compactor.
`live_only`	No	Specify if you want to retrieve live results only.
`report_id`	Yes	Provide a specific report ID.
`endpoint_id`	No	The ID of the endpoint to query.
`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: +{
+  "drilldown": {},
+  "drilldown_field": {},
+  "fields": {},
+  "group_fields": {},
+  "id": {},
+  "last_refresh": {},
+  "response_type": {},
+  "self": {},
+  "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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description's meaningful addition is the 'Perm: view_reports' authorization requirement, which annotations do not convey. It says nothing about pagination behavior, the size of result sets, or rate limits, despite pagination being central to a 50k-limit row tool.

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?

Four short sentences, front-loaded with the action and ending with the permission requirement, which is a sensible placement. The second sentence ('Gets data organized by report rows') largely restates the first and earns little.

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?

An output schema exists, so return values need not be explained, and the permission hint covers a real gap. But for a 13-parameter tool in a crowded report-tool namespace, the description leaves the agent without enough to choose confidently between this, get_drilldown_for_report_row, and get_export_for_report.

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 13 parameters are documented in the schema itself; the baseline of 3 applies. The description adds only the generic 'use parameters to filter' remark and no extra meaning for high-value parameters like details, verbose, live_only, or auto_paginate.

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?

States a verb and resource ('Get report rows', 'data organized by report rows'), but the phrasing is circular and never explains what a report row actually is. With siblings such as get_drilldown_for_report_row, get_export_for_report, list_report_errors, and requery_report, the description does nothing to differentiate this row-listing tool from adjacent report tools.

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?

'Use parameters to filter out returned results' implies filtering is the intended usage pattern, and 'Perm: view_reports' states a concrete prerequisite, which is genuinely useful. However, there is no when-to-use vs when-not guidance and no mention of when to prefer cursor/auto_paginate over from/limit, nor when to use this versus the drilldown or export siblings.

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

Deploy Server