action1-mcp-server

Delete additional action from version of Software Repository package

action1_delete_package_version_action

DestructiveIdempotent

Deletes a specified action from a Software Repository package version, with dry-run preview and required confirmation before execution.

Instructions

Delete additional action from version of Software Repository package. Perm: manage_software_repository.

Input Schema

Name	Required	Description
`org_id`	No	Org UUID.
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.
`action_id`	Yes	Provide a specific action ID.
`package_id`	Yes	Provide a specific package ID.
`version_id`	Yes	Provide a specific version ID.

Output Schema

Name	Required	Description	Default
`id`	No
`tool`	No
`type`	No
`status`	No
`dry_run`	No
`would_send`	No
`user_message`	No
`developer_message`	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"
```
- 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 / developer_message
```
Added value: +{}
```
- addedOutput schema / properties / dry_run
```
Added value: +{}
```
- addedOutput schema / properties / id
```
Added value: +{}
```
- addedOutput schema / properties / status
```
Added value: +{}
```
- addedOutput schema / properties / tool
```
Added value: +{}
```
- addedOutput schema / properties / type
```
Added value: +{}
```
- addedOutput schema / properties / user_message
```
Added value: +{}
```
- addedOutput schema / properties / would_send
```
Added value: +{}
```
First observedv0.5.0Jun 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds the required permission ('manage_software_repository'), which is genuinely useful authorization context. However, it doesn't mention the confirm="YES"/dry_run safety flow, which matters for a destructive operation.

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?

Two terse sentences, front-loaded and free of filler. Tight, though one sentence is a near-verbatim echo of the title.

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 a rich output schema and full annotation set, the essentials are covered. Still, for a destructive multi-ID operation it omits any note about irreversibility or the preview-by-default behavior that an agent calling this should account for.

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 six parameters are documented in the schema. The description adds no parameter semantics beyond that, which is acceptable given the schema does the heavy lifting.

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

Purpose4/5

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

Specific verb+resource: deletes an 'additional action' from a version of a Software Repository package. Clear enough to invoke, though it just restates the title and doesn't distinguish itself from similarly-named siblings like action1_delete_automation_action or action1_delete_version.

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 use this vs. alternatives (e.g., delete_version, delete_package, delete_automation_action) or preconditions beyond the permission string. The agent must infer the scenario entirely.

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

Deploy Server