action1-mcp-server

Run a data collection

action1_run_data_collection

Destructive

Trigger the run_data_collection template on an endpoint or endpoint group, with a dry-run preview and confirmation guard before execution.

Instructions

Trigger the run_data_collection template on an endpoint.

Input Schema

Name	Required	Description
`name`	No	Friendly action name.
`org_id`	No	Org UUID.
`params`	No	Optional template params.
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.
`endpoint_id`	Yes	Endpoint UUID, or Group ID when target_type='EndpointGroup'.
`target_type`	No	Endpoint (default) or EndpointGroup for fan-out.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description	Default
No arguments

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"

addedInput schema / properties / params / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

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

First observedv0.5.0Jun 27, 2026

TDQS

C2.5/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the risk profile is known. The description adds nothing beyond them: it never mentions that execution requires confirm="YES", that dry_run defaults to true/preview, or that target_type='EndpointGroup' fans out across endpoints — all of which materially change agent behavior.

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?

A single short sentence with no waste, but the brevity comes from omission rather than compression — it is front-loaded only trivially and provides no structure for the destructive, multi-mode operation it names.

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?

For an 8-parameter, destructive, fan-out-capable tool with a nested params object, a one-line description is insufficient. The confirm/dry_run safety gate and the Endpoint vs EndpointGroup targeting semantics are critical context that is left entirely to the schema, and an output schema does exist but the execution model still needs stating.

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 every parameter including confirm, dry_run, target_type and params is documented in the schema; baseline 3 applies. The description contributes no additional meaning about parameter interactions or defaults.

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?

Names a verb ("Trigger") and the specific template (run_data_collection) on a target (endpoint), so the basic action is identifiable. However, the resource name is a template identifier with no explanation of what data collection produces, and it does not distinguish this from siblings like action1_execute_and_wait, action1_run_script, or action1_create_automation_instance.

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 guidance on when to choose this over the many automation-execution siblings, no prerequisites, and no exclusions. The agent must infer usage entirely from the name.

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

Deploy Server