action1-mcp-server

Update the report subscription

action1_update_report_subscription

Destructive

Modify an existing report subscription's schedule or report type. Use it to update daily or weekly patch statistics delivery settings by subscription ID.

Instructions

Update the report subscription. Updates the report subscription. Perm: view_reports.

Input Schema

Name	Required	Description
`body`	No	Request body (schema: ReportSubscriptionPayload)
`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
`self`	No
`tool`	No
`type`	No
`format`	No
`dry_run`	No
`comments`	No
`would_send`	No
`endpoint_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 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 / body / properties

Added value: +{
+  "name": {
+    "description": "URL of a user or API key assigned the role.\"",
+    "type": "string"
+  },
+  "report_id": {
+    "description": "ID of a report.",
+    "enum": [
+      "daily_patch_statistics",
+      "weekly_patch_statistics"
+    ],
+    "type": "string"
+  },
+  "schedule": {
+    "description": "Schedule settings string in the following format - **(ENABLED|DISABLED)...",
+    "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: +{}
```
addedOutput schema / properties / comments
```
Added value: +{}
```
addedOutput schema / properties / dry_run
```
Added value: +{}
```
addedOutput schema / properties / endpoint_count
```
Added value: +{}
```
addedOutput schema / properties / format
```
Added value: +{}
```
addedOutput schema / properties / id
```
Added value: +{}
```
addedOutput schema / properties / self
```
Added value: +{}
```
addedOutput schema / properties / tool
```
Added value: +{}
```
addedOutput schema / properties / type
```
Added value: +{}
```
addedOutput schema / properties / would_send
```
Added value: +{}
```

First observedv0.5.0Jun 27, 2026

TDQS

C2.2/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the permission string; it does not disclose what gets overwritten or lost, whether omitted fields are preserved, or how the destructive update behaves — notable for a mutation tool, and the mention of a "view" permission on a destructive update is confusing rather than clarifying.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description wastes an entire sentence restating the first verbatim ("Update the report subscription. Updates the report subscription."), which is pure duplication rather than front-loaded information. The permission note is the only non-redundant content.

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?

Given a destructive mutation with a nested body payload, a confirm/dry_run safety gate, and an output schema, the description should at minimum say what updating changes or reassure about the preview/confirm mechanism. Instead it supplies only a permission name, leaving the agent dependent entirely on schema and annotations.

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%, including documented subscription_id, confirm, dry_run, and nested body fields, so the schema does the heavy lifting and baseline 3 applies. The description adds no extra meaning about parameter interactions, such as that confirm must be "YES" and dry_run defaults to true.

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 says "Update the report subscription" and then repeats the same sentence, adding nothing beyond the tool name and title. It identifies the verb and resource but offers no detail about which aspects of the subscription are updatable, and it doesn't distinguish itself from list/create/delete/get report subscription siblings.

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?

There is no guidance on when to use this tool versus action1_create_report_subscription, action1_delete_report_subscription, or action1_list_report_subscriptions. The only extra text is "Perm: view_reports", which gives an auth hint but no usage context or prerequisites about the confirm/dry_run flow.

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

Deploy Server