Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

security-remove-user

Destructive

Removes a Sitecore user account by identity, enabling administrators to revoke access and remove obsolete accounts.

Instructions

Removes the 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>"
    },
    "name": "security-remove-user"
  }
}

Input Schema

NameRequiredDescriptionDefault
identityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known. The description adds no behavioral context beyond restating removal: it does not mention permissions, reversibility, side effects, or what happens to related data.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no filler. It is efficient, though extremely terse for a destructive operation.

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 destructive one-parameter tool, the description should at least clarify the identity format and any prerequisites. Annotations cover the safety signal, but the description leaves key invocation details absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required 'identity' parameter. The description never explains whether identity is a username, email, GUID, or domain-qualified name, so it fails to compensate for the missing schema documentation.

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 clear verb and resource: 'Removes' plus 'the Sitecore user.' An agent can identify the operation, but the description does not distinguish it from nearby siblings such as security-disable-user or security-remove-role-member.

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 guidance, no alternative tool recommendation, and no prerequisite or warning. The agent must infer all usage context from the tool name alone.

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