action1-mcp-server

Create new user

action1_create_user

Destructive

Create a new Action1 user account with email, name, and credentials, optionally as an SSO user. Preview with dry run before executing.

Instructions

Create new user. Creates a new user. To create an SSO user, please first review the following documentation: -. Perm: manage_users.

Input Schema

Name	Required	Description
`body`	Yes	Request body
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.

Output Schema

Name	Required	Description	Default
`tool`	No
`value`	No
`dry_run`	No
`would_send`	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"

removedInput schema / properties / body / additionalProperties
```
Removed value: -{}
```

addedInput schema / properties / body / anyOf

Added value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "email": {
+        "type": "string"
+      },
+      "enabled": {
+        "description": "Defines if the user is enabled or disabled.",
+        "enum": [
+          "yes",
+          "no"
+        ],
+        "type": "string"
+      },
+      "first_name": {
+        "type": "string"
+      },
+      "last_name": {
+        "type": "string"
+      },
+      "password": {
+        "description": "When creating API credentials, the Enterprise Admin can read the password.",
+        "type": "string"
+      },
+      "phone": {
+        "type": "string"
+      },
+      "session_timeout": {
+        "description": "The session timeout in seconds for API and GUI.",
+        "type": "number"
+      },
+      "timezone": {
+        "description": "Timezone identifier.",
+        "type": "string"
+      },
+      "user_type": {
+        "const": "Interactive",
+        "type": "string"
+      }
+    },
+    "required": [
+      "email",
+      "first_name",
+      "last_name",
+      "password"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": {},
+    "properties": {
+      "email": {
+        "type": "string"
+      },
+      "enabled": {
+        "description": "Defines if the user is enabled or disabled.",
+        "enum": [
+          "yes",
+          "no"
+        ],
+        "type": "string"
+      },
+      "first_name": {
+        "type": "string"
+      },
+      "last_name": {
+        "type": "string"
+      },
+      "phone": {
+        "type": "string"
+      },
+      "session_timeout": {
+        "description": "The session timeout in seconds for API and GUI.",
+        "type": "number"
+      },
+      "timezone": {
+        "description": "Timezone identifier.",
+        "type": "string"
+      },
+      "user_type": {
+        "const": "Interactive",
+        "type": "string"
+      }
+    },
+    "required": [
+      "email"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": {},
+    "properties": {
+      "email": {
+        "type": "string"
+      },
+      "enabled": {
+        "description": "Defines if the user is enabled or disabled.",
+        "enum": [
+          "yes",
+          "no"
+        ],
+        "type": "string"
+      },
+      "first_name": {
+        "type": "string"
+      },
+      "password": {
+        "description": "When creating API credentials, the Enterprise Admin can read the password.",
+        "type": "string"
+      },
+      "timezone": {
+        "description": "Timezone identifier.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "enabled",
+      "email",
+      "password",
+      "first_name"
+    ],
+    "type": "object"
+  }
+]

changedInput schema / properties / body / description

Previous value: -"Request body (schema: object)"New value: +"Request body"

removedInput schema / properties / body / type
```
Removed value: -"object"
```

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 / dry_run
```
Added value: +{}
```
addedOutput schema / properties / tool
```
Added value: +{}
```
addedOutput schema / properties / value
```
Added value: +{}
```
addedOutput schema / properties / would_send
```
Added value: +{}
```

First observedv0.5.0Jun 27, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, so the safety profile is covered. The description adds one genuinely non-structured fact — the required 'manage_users' permission — but says nothing about duplicate-email behavior, password handling, or how SSO creation differs, and the promised SSO documentation pointer is blank.

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 opening is wasted duplication ('Create new user. Creates a new user.') and the SSO sentence ends in a dangling 'documentation: -' fragment. Neither the permission line nor the broken reference is front-loaded in a way that helps invocation.

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 safety, so the description is not required to explain returns. However, for a destructive user-creation mutation it omits the SSO path it advertises, and the only unique behavioral detail (permission requirement) is a single trailing tag.

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% and the nested body variants are documented, so the schema carries the parameter burden. The description adds no meaning to any parameter — even the SSO hint, which would plausibly relate to a body field, points at an empty reference.

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?

The verb+resource ('create user') is identifiable, but the first two sentences are the same statement repeated ('Create new user. Creates a new user.') and nothing distinguishes this from sibling user/role tools such as action1_create_role_user or action1_update_user. An agent knows what it does but not why it would pick this over its 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?

The only guidance offered is 'To create an SSO user, please first review the following documentation: -' where the link is empty, making the hint unusable. The 'Perm: manage_users' note tells the agent the required permission, but there is no when-to-use / when-not-to-use framing or mention of alternatives.

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

Deploy Server