action1-mcp-server

List reports

action1_list_reports

Read-onlyIdempotent

Retrieve existing enterprise-wide reports and optionally include the full report subtree or skip per-item compaction to control output detail.

Instructions

List reports. Gets a list of existing reports. At this time all reports are enterprise-wide.

Input Schema

Name	Required	Description
`subtree`	No	Specify if you want to query the entire report subtree.
`verbose`	No	Skip per-item compactor.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`items`	Yes
`total`	No
`truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

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: +{
+  "alertable": {},
+  "builtin": {},
+  "children": {},
+  "column_aliases": {},
+  "data_sources": {},
+  "data_sourses": {},
+  "description": {},
+  "drilldown_columns": {},
+  "filter_set": {},
+  "id": {},
+  "large_image": {},
+  "long_description": {},
+  "name": {},
+  "parent_category": {},
+  "report_data": {},
+  "report_errors": {},
+  "self": {},
+  "simple": {},
+  "simple_columns": {},
+  "small_image": {},
+  "summary_columns": {},
+  "summary_customizable": {},
+  "type": {}
+}

First observedv0.5.0Jun 27, 2026

TDQS

C2.8/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 adds one genuinely useful behavioral fact — results are always enterprise-wide, so no org-level filtering exists — but says nothing about pagination, result volume, or ordering. With annotations carrying most of the burden, a 3 is appropriate.

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?

Three short sentences, but the first two say the same thing twice, which wastes the front-loaded position. The one informative clause (enterprise-wide scope) is buried last rather than leading.

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?

With an output schema present and rich annotations, the description needn't explain return values, and the schema covers all parameters. However, for a list tool in a crowded report family, it omits result-set size/pagination expectations and any hint of how the output is shaped at enterprise scope.

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% and all three parameters (subtree, verbose, response_format) are documented in the schema, so the baseline is 3. The description adds no meaning beyond the schema — notably it never explains when 'subtree' matters or what 'verbose' changes about output.

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 verb+resource (list reports) is identifiable, but the first two sentences are near-tautologies that merely restate the name and title ("List reports. Gets a list of existing reports."). The one substantive clause — all reports are enterprise-wide — clarifies scope but does not distinguish this tool from siblings such as action1_get_report_or_category or action1_list_report_data.

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 when-to-use guidance, no exclusions, and no mention of alternatives among the many report-related siblings (get_report_or_category, list_report_data, list_report_errors, create_report). The enterprise-wide note is a scope constraint, not invocation guidance.

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

Deploy Server