Skip to main content
Glama
adamcmyhre

Salesforce MCP Pro

by adamcmyhre

sf_remove_permset_group

Remove one or more permission set groups from a Salesforce user. Specify group names and target org to revoke access.

Instructions

Remove one or more permission set groups from a user in Salesforce.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNo
directoryNo
targetOrgNo
onBehalfOfUserNo
permissionSetGroupNamesYes
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only states the core action. It does not mention that this is a destructive operation, whether confirmation is needed, or how it affects existing permissions. The presence of a 'confirm' parameter is not explained.

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 concise sentence that immediately communicates the core function. It is not verbose, though possibly too brief to be fully useful.

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?

Given the tool has five parameters, no annotations, and no output schema, a single sentence is insufficient. The description lacks information about required context (e.g., target org, user identity), the meaning of confirmation, and the operational impact.

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

Parameters2/5

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

The schema has 0% description coverage and the description does not explain any parameters. It implies 'permissionSetGroupNames' are the groups to remove, but leaves 'confirm', 'directory', 'targetOrg', and 'onBehalfOfUser' completely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool removes one or more permission set groups from a user in Salesforce, using a specific verb and resource. It differentiates from sibling tools like sf_remove_permission_set by explicitly referring to 'permission set groups'.

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?

The description provides no guidance on when to use this tool versus alternatives such as sf_remove_permission_set or sf_assign_permset_group. It does not mention any prerequisites or contexts.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adamcmyhre/Salesforce-MCP-Pro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server