action1-mcp-server

Export a report

action1_get_export_for_report

Read-onlyIdempotent

Exports data from a specified Action1 report, applying optional filters, sorting, pagination, and CSV or HTML output for reporting and analysis.

Instructions

Export a report. Exports data from the report. Use parameters to filter out exported data. 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).
`filter`	No	Provide a case-insensitive substring to filter and narrow down returned results (i.e., if...
`format`	No	Specify the report format.
`org_id`	No	Org UUID.
`sortby`	No	Define the sorting order by a certain field.
`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.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description	Default
`value`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 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"

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 / value
```
Added value: +{}
```

First observedv0.5.0Jun 27, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds only the required permission ('Perm: view_reports'), which is useful, but it omits behavior that matters for an export tool with 10 parameters, such as pagination behavior, maximum page size, format implications, or whether the export is synchronous.

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 short and front-loaded, which is good, but the second sentence ('Exports data from the report') merely restates the first ('Export a report'). The third sentence is vague rather than informative, so several words do not earn their place.

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 and the input schema is rich, so the description need not explain return values or every parameter. However, for a 10-parameter export tool in a crowded sibling group, it is thin on routing guidance and behavioral expectations, leaving the agent to rely almost entirely on structured fields.

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 ten parameters are already documented in the input schema, including enums for format, live_only, and response_format. The description only says to 'use parameters to filter,' adding no specific meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource ('Export a report') and repeats that it exports report data. However, it does not distinguish this tool from close siblings such as action1_report_export, action1_list_report_data, or action1_get_export_for_report_row, so an agent cannot reliably tell which export tool to choose from the description alone.

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?

The only usage hint is 'Use parameters to filter out exported data,' which does not explain when to use this tool instead of alternatives like listing report data or exporting a single report row. There are no stated preconditions, exclusions, or sibling routing cues beyond the permission note.

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

Deploy Server