SmartBear MCP server

Official

by SmartBear

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Contract Testing: Admin Update User

contract-testing_admin_update_user

Idempotent

Update a user's profile details or active status by user ID, including name, email, first name, last name, and account activation.

Instructions

Update a user's profile or active status (admin).

Toolset: Admin

Parameters:

userId (string) required: UUID of the user to update
active (boolean): Whether the user is active
email (string): New email address
firstName (string): First name
lastName (string): Last name
name (string): Display name

Input Schema

Name	Required	Description
`name`	No	Display name
`email`	No	New email address
`active`	No	Whether the user is active
`userId`	Yes	UUID of the user to update
`lastName`	No	Last name
`firstName`	No	First name

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, idempotentHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds only the '(admin)' qualifier (elevated privileges implied) but says nothing about partial-update semantics — whether omitted fields are preserved or cleared — or what happens on email collisions, which is the key behavioral question for a 6-field patch-style update.

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. However, the enumerated parameter list duplicates the input schema word-for-word at 100% coverage, consuming space without adding information that would otherwise be unavailable to the agent.

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, so return-value explanation is not required, and parameters are fully covered by the schema. Still missing for a mutation tool: partial-update semantics, required permissions, and error conditions (duplicate email, unknown userId). Adequate but with clear gaps.

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 structurally. The description's parameter block restates the schema descriptions verbatim, adding no format hints (UUID shape is only implied), no mutual-exclusivity rules, and no statement that only userId is required while the rest are optional patch fields. Baseline 3 applies when the schema does the work.

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 ('Update a user's profile or active status (admin)') and the title scopes it to the admin surface. It is distinguishable from contract-testing_admin_create_user and contract-testing_admin_delete_user by the verb, though no sibling is named explicitly.

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?

No when-to-use or when-not-to-use guidance. The description does not tell the agent to use contract-testing_admin_get_user to read first, that role changes belong to contract-testing_admin_set_user_roles, or that team membership belongs to contract-testing_admin_patch_team_users, even though both sit adjacent in the sibling list.

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

Deploy Server