Skip to main content
Glama
Sign In
SitecoreMCP

SitecoreMCP

by ramseur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

security-set-user-password

Update Sitecore user passwords by specifying identity and new password, optionally requiring reset on next login or validating old password.

Instructions

Sets a new password for a Sitecore user.

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
resetPasswordNoIf true, the user will be required to change password on next login
oldPasswordNoThe old password. If provided, it will be validated before setting the new password

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.5

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool performs a write operation ('Sets'), implying mutation, but lacks details on permissions required, whether changes are logged or reversible, error conditions (e.g., invalid password policies), or response format. This is inadequate for a security-sensitive mutation tool.

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?

The description is a single, efficient sentence with zero waste—it directly states the tool's purpose without redundancy or fluff. It's appropriately front-loaded and sized for a straightforward tool.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks critical context such as authentication requirements, side effects (e.g., password history), error handling, or return values. Given the security sensitivity and potential for misuse, this minimal description fails to provide adequate guidance.

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%, with each parameter well-documented in the schema (e.g., identity format, password validation). The description adds no additional parameter semantics beyond implying password setting, which the schema already covers comprehensively. Baseline 3 is appropriate as 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 clearly states the action ('Sets') and target ('a new password for a Sitecore user'), providing a specific verb+resource combination. However, it doesn't differentiate from potential siblings like 'security-set-user' or 'security-unlock-user' that might also modify user properties, leaving room for ambiguity in a security-focused toolset.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., admin permissions), exclusions (e.g., not for system accounts), or related tools like 'security-unlock-user' for locked accounts, leaving the agent to infer usage context solely from the tool name and parameters.

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