action1-mcp-server

Update a setting

action1_update_setting

Destructive

Update an existing Action1 setting by ID to change its scope or value. Supports preview via dry run and requires confirmation before applying changes.

Instructions

Update a setting. Updates an existing setting specified by its ID. Perm: manage_advanced_settings.

Input Schema

Name	Required	Description
`body`	No	Request body (schema: SettingPayload)
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.
`setting_id`	Yes	Provide a specific setting ID.

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`self`	No
`tool`	No
`type`	No
`scope`	No
`value`	No
`dry_run`	No
`value_type`	No
`would_send`	No
`description`	No
`template_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 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: +{
+  "scope": {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "object": {
+          "description": "Select specific organization, group, or apply everywhere. Accepts: all, {orgId}, {groupId}.",
+          "type": "string"
+        },
+        "type": {
+          "description": "The scope to apply the setting to.",
+          "enum": [
+            "Enterprise",
+            "Organization",
+            "Group"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "type",
+        "object"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "value": {
+    "description": "The value defined for this setting.",
+    "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 / description
```
Added value: +{}
```
addedOutput schema / properties / dry_run
```
Added value: +{}
```
addedOutput schema / properties / id
```
Added value: +{}
```
addedOutput schema / properties / name
```
Added value: +{}
```
addedOutput schema / properties / scope
```
Added value: +{}
```
addedOutput schema / properties / self
```
Added value: +{}
```
addedOutput schema / properties / template_id
```
Added value: +{}
```
addedOutput schema / properties / tool
```
Added value: +{}
```
addedOutput schema / properties / type
```
Added value: +{}
```
addedOutput schema / properties / value
```
Added value: +{}
```
addedOutput schema / properties / value_type
```
Added value: +{}
```
addedOutput schema / properties / would_send
```
Added value: +{}
```

First observedv0.5.0Jun 27, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already disclose that this is destructive, non-idempotent, and open-world, so the description carries a lighter burden. It usefully adds the required permission ("manage_advanced_settings"), but does not explain destructive effects, reversibility, or the preview/execute workflow around dry_run and confirm.

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?

The description is short and front-loaded, with the permission requirement separated cleanly. The first sentence restates the tool name and title, so there is a small amount of redundancy, but overall it is appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has rich schema coverage, annotations, and an output schema, so the description need not explain parameter details or return values. It includes the key permission requirement, though it could mention the confirm/dry_run execution model for a destructive update.

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 the schema itself documents setting_id, body, confirm, and dry_run. The description only adds that the setting is specified by ID, which is already conveyed by the schema; 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.

Purpose4/5

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

The description gives a specific verb+resource ("Update a setting") and clarifies that it updates an existing setting identified by ID. It does not explicitly differentiate this from the sibling create/get/delete setting tools, but the operation itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "Updates an existing setting specified by its ID" implies the usage context, but there is no explicit guidance on when to use this versus create_setting, get_setting, or delete_setting. No exclusions or prerequisites beyond the permission note are provided.

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

Deploy Server