SmartBear MCP server

Official

Overview Schema Source Related Servers Discussions Admin

Contract Testing: Admin Create User

contract-testing_admin_create_user

Create a new admin user account for contract testing by providing an email and display name, plus optional first/last name and SSO identity details.

Instructions

Create a new user account (admin).

Toolset: Admin

Parameters:

email (string) required: Email address of the new user
name (string) required: Display name of the new user
firstName (string): First name
lastName (string): Last name
externalIdpId (string): External identity provider ID (for SAML/SSO)
externalIdpUsername (string): External IdP username (for SAML/SSO)

Input Schema

Name	Required	Description
`name`	Yes	Display name of the new user
`email`	Yes	Email address of the new user
`lastName`	No	Last name
`firstName`	No	First name
`externalIdpId`	No	External identity provider ID (for SAML/SSO)
`externalIdpUsername`	No	External IdP username (for SAML/SSO)

Output Schema

Name	Required	Description	Default
`name`	No
`type`	No
`uuid`	No
`email`	No
`_links`	No
`active`	No
`lastName`	No
`seatType`	No
`_embedded`	No
`createdAt`	No
`firstName`	No
`lastLogin`	No
`updatedAt`	No
`externalId`	No
`externalIdpId`	No
`typeDescription`	No
`identityProviderId`	No
`externalIdpUsername`	No
`authenticationSource`	No
`lastTimeTokenAccessed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.43.0Nov 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "EmbeddedLink": {
+      "additionalProperties": {},
+      "properties": {
+        "href": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "templated": {
+          "type": "boolean"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "Permission": {
+      "additionalProperties": {},
+      "properties": {
+        "description": {
+          "type": "string"
+        },
+        "group": {
+          "type": "string"
+        },
+        "label": {
+          "type": "string"
+        },
+        "scope": {
+          "type": "string"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "UserRole": {
+      "additionalProperties": {},
+      "properties": {
+        "_links": {
+          "additionalProperties": {},
+          "properties": {
+            "self": {
+              "$ref": "#/$defs/EmbeddedLink"
+            }
+          },
+          "type": "object"
+        },
+        "name": {
+          "type": "string"
+        },
+        "permissions": {
+          "items": {
+            "$ref": "#/$defs/Permission"
+          },
+          "type": "array"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "UserTeam": {
+      "additionalProperties": {},
+      "properties": {
+        "_links": {
+          "additionalProperties": {},
+          "properties": {
+            "pf:integrations": {
+              "$ref": "#/$defs/EmbeddedLink"
+            },
+            "pf:membership": {
+              "$ref": "#/$defs/EmbeddedLink"
+            },
+            "self": {
+              "$ref": "#/$defs/EmbeddedLink"
+            }
+          },
+          "type": "object"
+        },
+        "name": {
+          "type": "string"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "_embedded": {
+      "additionalProperties": {},
+      "properties": {
+        "roles": {
+          "items": {
+            "$ref": "#/$defs/UserRole"
+          },
+          "type": "array"
+        },
+        "teams": {
+          "items": {
+            "$ref": "#/$defs/UserTeam"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "_links": {
+      "additionalProperties": {},
+      "properties": {
+        "pf:tokens": {
+          "$ref": "#/$defs/EmbeddedLink"
+        },
+        "self": {
+          "$ref": "#/$defs/EmbeddedLink"
+        }
+      },
+      "type": "object"
+    },
+    "active": {
+      "type": "boolean"
+    },
+    "authenticationSource": {
+      "type": "string"
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "email": {
+      "type": "string"
+    },
+    "externalId": {
+      "type": "string"
+    },
+    "externalIdpId": {
+      "type": "string"
+    },
+    "externalIdpUsername": {
+      "type": "string"
+    },
+    "firstName": {
+      "type": "string"
+    },
+    "identityProviderId": {
+      "type": "string"
+    },
+    "lastLogin": {
+      "type": "string"
+    },
+    "lastName": {
+      "type": "string"
+    },
+    "lastTimeTokenAccessed": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "seatType": {
+      "type": "string"
+    },
+    "type": {
+      "anyOf": [
+        {
+          "const": 0,
+          "type": "number"
+        },
+        {
+          "const": 1,
+          "type": "number"
+        }
+      ]
+    },
+    "typeDescription": {
+      "type": "string"
+    },
+    "updatedAt": {
+      "type": "string"
+    },
+    "uuid": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Addedv0.40.0Sep 3, 2026
Removedv0.34.0Aug 7, 2026
First observedv0.27.1Jun 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the write/mutation nature is covered outside the description. The description adds no behavior beyond that: it does not say whether the account is immediately active or pending, whether a welcome email is dispatched, whether duplicate emails error, or what permission level is required.

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 opening sentence is front-loaded and efficient, but the parameter list and toolset header duplicate structured data the agent already has, roughly doubling the length without adding information.

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 an output schema present and full schema description coverage, return values and argument shapes are already handled, so the remaining burden is small. Still, for an admin mutation that creates an identity, the description omits the activation semantics and duplicate-email behavior an agent would need to predict outcomes.

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 every parameter is already documented in the input schema, and the description's parameter block simply restates those same strings verbatim. The only marginally useful addition is flagging email and name as required, which the schema's required array already conveys.

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?

States a specific verb and resource: 'Create a new user account (admin)', which an agent can distinguish from contract-testing_admin_update_user, contract-testing_admin_invite_users, and contract-testing_admin_create_system_account. It does not, however, explicitly say how it differs from invite_users, which is the nearest overlapping sibling.

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 when-to-use or when-not-to-use guidance at all. The description never says when an agent should create a user directly versus issuing an invite, nor what prerequisites (admin role, existing team) must hold.

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

Deploy Server