Skip to main content
Glama
semwalajay83-sem

salesforce-metadata-mcp

Create Salesforce User

sf_create_user

Create a Salesforce user with required username, lastName, email, and an existing profile, optionally assigning a role.

Instructions

Creates a new Salesforce user via the REST API. Requires username (must be unique and email-like), lastName, email, and profileName. The profile must already exist. Optionally assign a role by roleApiName (DeveloperName of the UserRole). The user will receive a welcome email unless email confirmations are suppressed in org settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aliasYesUser alias (max 8 chars, shown in list views)
emailYesEmail address (also used for notifications)
localeNoLocale, e.g. 'en_US'en_US
lastNameYesLast name
roleNameNoRole name to assign, e.g. 'CEO'
timeZoneNoTimezone, e.g. 'America/New_York'America/Los_Angeles
usernameYesUnique username (must be email format and unique across all Salesforce orgs)
firstNameNoFirst name
profileNameYesProfile name, e.g. 'Standard User', 'System Administrator'
emailEncodingNoEmail encodingUTF-8
languageLocaleNoLanguage and locale, e.g. 'en_US'en_US
Behavior4/5

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

Annotations indicate a non-read-only, mutating operation, but the description adds specific behavioral details beyond that: the user will receive a welcome email unless suppressed, and the role option requires the DeveloperName. It also notes the REST API mechanism. This provides useful context that annotations do not cover, though it does not mention all side effects or the return format.

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 extremely concise, with three sentences that front-load the core action and requirements. Every sentence provides necessary information: the action, the required fields, the prerequisite, optional role assignment, and the email side effect. There is no verbose or redundant content.

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's complexity (11 parameters) and the lack of an output schema, the description is incomplete. It covers the main required fields and one side effect, but it does not describe the return value or success/error behavior. More importantly, the role parameter naming conflict (roleApiName vs. roleName) creates a credibility gap, and the description omits clarification of other parameters' semantics that might be non-obvious. Overall, it is not sufficiently complete for an agent to use reliably.

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 covers all 11 parameters with descriptions, so the baseline is 3. However, the description introduces a significant discrepancy by referring to 'roleApiName' while the schema parameter is 'roleName'. This could mislead an agent into looking for a non-existent parameter. The description adds little other semantic value beyond the schema, and the naming mismatch undermines its usefulness.

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's purpose: 'Creates a new Salesforce user via the REST API.' It uses a specific verb (creates) and resource (Salesforce user), and the distinct focus on creation distinguishes it from sibling tools like sf_update_user. The description also enumerates the required fields, reinforcing the purpose.

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?

The description provides clear context for use by listing required fields ('Requires username, lastName, email, and profileName') and stating a prerequisite ('The profile must already exist'). It also clarifies an optional behavior (assigning a role). However, it does not explicitly mention alternatives or when not to use this tool (e.g., for updating existing users), so it lacks explicit exclusion criteria.

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/semwalajay83-sem/salesforce-metadata-mcp'

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