action1-mcp-server

Delete the report subscription

action1_delete_report_subscription

DestructiveIdempotent

Delete a report subscription by ID, with preview by default and explicit confirmation required before removal.

Instructions

Delete the report subscription. Removes the report subscription.

Input Schema

Name	Required	Description
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.
`subscription_id`	Yes	Provide a specific subscription 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

C2.4/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the key safety profile is structured elsewhere. The description adds nothing beyond "Removes," which merely repeats the destructive nature already conveyed by annotations and the name. It does not explain confirmation requirements, execution behavior, or consequences.

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, but the second sentence ("Removes the report subscription") is redundant with the first and the tool name. It is not verbose, but the repetition does not earn its 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 annotations cover the destructive, idempotent, and open-world behavior, reducing what the prose must carry. However, for a destructive deletion tool with a required confirmation string and a dry-run default, the description could usefully mention the preview/confirm workflow rather than leaving it entirely to schema 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 subscription_id, confirm, and dry_run are fully documented in the schema. The description adds no parameter meaning beyond that, so baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose2/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 ("Delete the report subscription") but only restates the tool name/title. It does not distinguish this deletion tool from sibling tools such as update_report_subscription or list_report_subscriptions. This is essentially a tautological restatement rather than added explanatory value.

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?

It gives no guidance on when to use this tool versus alternatives, nor any prerequisites or warnings. The schema's confirm and dry_run fields imply a safety workflow, but the description does not explain that workflow or route agents to sibling tools.

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

Deploy Server