Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

security-remove-role-member

Destructive

Remove users or roles from a Sitecore role by providing the role identity and comma-separated members, keeping access permissions accurate.

Instructions

Removes members from a Sitecore role.

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>",
      "members": "<members>"
    },
    "name": "security-remove-role-member"
  }
}

Input Schema

NameRequiredDescriptionDefault
membersYesThe members to remove from the role (comma-separated list of users or roles, e.g. 'sitecore\user1,sitecore\user2')
identityYesThe identity of the role to remove members from (e.g. 'CustomRole' or full path 'sitecore\CustomRole')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true, so the danger is conveyed. The description adds nothing beyond that: no mention of irreversibility, whether identities are case-sensitive, what happens if a member is absent, or whether the operation is transactional across the comma-separated list.

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?

A single, front-loaded sentence with no filler. Nothing to trim.

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 mutation with no output schema, the description is too thin. It should say what is destroyed (role membership entries only, not the users/roles themselves), whether the action is reversible, and confirm behavior when a listed member is not in the role.

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 both parameters documented including a comma-separated example for 'members' and a path example for 'identity'. Baseline 3 applies since the schema already carries full semantics.

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 (removes) and resource (members) scoped to Sitecore roles. Clear enough to distinguish from security-add-role-member and security-get-role-member, though it doesn't explicitly name those siblings.

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 guidance, no prerequisites. With sibling security-add-role-member right there, a routing hint would have been trivial to add, but none is present.

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