Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

security-set-user-password

Set a new password for a Sitecore user by validating the current password or using an administrative reset flag.

Instructions

Sets a new password for a Sitecore user. Supply either 'oldPassword' (validated before the change) or 'resetPassword: true' (an administrative reset that does not need the current password) — SPE offers no third way to change a password.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identity": "<identity>",
      "newPassword": "<newPassword>"
    },
    "name": "security-set-user-password"
  }
}

Input Schema

NameRequiredDescriptionDefault
identityYesThe identity of the user to update the password for (e.g. 'admin' or full path 'sitecore\admin')
newPasswordYesThe new password for the user
oldPasswordNoThe user's current password, validated before the change. Supply this or 'resetPassword: true'.
resetPasswordNoAdministrative reset: change the password without knowing the current one. Supply this or 'oldPassword'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation nature is covered; the description adds that oldPassword is validated before the change and that resetPassword bypasses the current-password requirement as an administrative action. It does not mention that an administrative reset typically requires elevated privileges or what happens on validation failure, leaving a modest gap.

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

Conciseness5/5

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

Two sentences, front-loaded with the core action and then the mode-selection rule. No filler; the em-dash clause adds a genuine constraint rather than padding.

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?

For a four-parameter mutation with no output schema, the description covers the essential branch logic and both parameter paths are fully documented in the schema. It omits permission requirements for the administrative reset and failure behavior, which are the main remaining details an agent would want.

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 baseline is 3. The description's 'supply either oldPassword or resetPassword: true' restates what the schema already says in each parameter's own description, adding little beyond the mutual-exclusivity framing.

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 ('Sets a new password for a Sitecore user'), which is immediately distinguishable from sibling mutations like security-set-user, security-disable-user, and security-unlock-user. It does not explicitly name a sibling or contrast itself with them, but the resource+action combination 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 Guidelines4/5

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

Gives clear operational context for the two invocation modes (validated old password vs. administrative reset) and asserts there is no third path, which helps an agent pick the right call shape. It stops short of saying when to prefer this tool over siblings such as security-set-user or security-new-user, so no exclusions 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

Other Tools