Skip to main content
Glama
sunny980123

Salesforce MCP Server

by sunny980123

Create Salesforce Record

salesforce_create_record

Create a new record in Salesforce for any object type by specifying fields and values. Returns the new record ID.

Instructions

Create a new record in Salesforce.

Args:

  • object_type (string): The Salesforce object type (e.g., 'Account', 'Contact', 'Lead')

  • fields (object): Key-value pairs of field API names and their values

Returns: { id: string, success: boolean } - The new record ID on success.

Common required fields:

  • Account: Name (required)

  • Contact: LastName (required), AccountId (optional)

  • Lead: LastName + Company (required)

  • Opportunity: Name + StageName + CloseDate (required)

  • Case: Subject (required)

Examples:

  • Create account: object_type='Account', fields={ "Name": "Acme Corp", "Industry": "Technology" }

  • Create lead: object_type='Lead', fields={ "FirstName": "John", "LastName": "Doe", "Company": "Acme", "Email": "john@acme.com" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesField values as key-value pairs. Keys are Salesforce field API names.
object_typeYesSalesforce object type to create (e.g., Account, Contact, Opportunity)
Behavior4/5

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

The description adds behavioral context beyond annotations: it specifies the return format (id, success), lists common required fields per object type, and provides examples. This compensates for the few annotations, though it does not mention error handling or permissions.

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 well-structured with sections for args, returns, common fields, and examples. It is concise and front-loaded with the main purpose, no unnecessary words.

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

Completeness4/5

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

Given the tool complexity (create with object_type and fields), the description covers return value, examples, and field requirements. It is mostly complete but lacks mention of potential errors, rate limits, or authentication, which would be helpful.

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

Parameters5/5

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

The description adds significant value beyond the schema: it documents common required fields for multiple object types and provides concrete examples. The schema has 100% coverage, but the description deepens understanding.

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 purpose: 'Create a new record in Salesforce.' It uses a specific verb and resource, and distinguishes from sibling tools like salesforce_get_record, salesforce_update_record, and salesforce_delete_record.

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 does not provide explicit guidance on when to use this tool versus alternatives such as salesforce_update_record or salesforce_query. It lacks context for usage boundaries.

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/sunny980123/Salesforce-MCP-Server'

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