Skip to main content
Glama
smn2gnt

MCP Salesforce Connector

by smn2gnt

create_record

Generate Salesforce records by specifying the object name and data. Integrate with Salesforce Connector to manage CRM data effectively via API operations.

Instructions

Creates a new record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe data for the new record
object_nameYesThe name of the Salesforce object (e.g., 'Account', 'Contact')

Implementation Reference

  • The handler logic for the 'create_record' tool. It extracts object_name and data from arguments, validates them, connects to Salesforce if needed, creates the record using simple-salesforce's create method, and returns the result as JSON.
    elif name == "create_record":
        object_name = arguments.get("object_name")
        data = arguments.get("data")
        if not object_name or not data:
            raise ValueError("Missing 'object_name' or 'data' argument")
        if not sf_client.sf:
            raise ValueError("Salesforce connection not established.")
        sf_object = getattr(sf_client.sf, object_name)
        results = sf_object.create(data)
        return [
            types.TextContent(
                type="text",
                text=f"Create {object_name} Record Result (JSON):\n{json.dumps(results, indent=2)}",
            )
        ]
  • Registration of the 'create_record' tool in the list_tools handler, including its description and input schema for object_name and data.
    types.Tool(
        name="create_record",
        description="Creates a new record",
        inputSchema={
            "type": "object",
            "properties": {
                "object_name": {
                    "type": "string",
                    "description": "The name of the Salesforce object (e.g., 'Account', 'Contact')",
                },
                "data": {
                    "type": "object",
                    "description": "The data for the new record",
                    "properties": {},
                    "additionalProperties": True,
                },
            },
            "required": ["object_name", "data"],
        },
    ),
  • Input schema definition for the 'create_record' tool, specifying required object_name (string) and data (object).
    types.Tool(
        name="create_record",
        description="Creates a new record",
        inputSchema={
            "type": "object",
            "properties": {
                "object_name": {
                    "type": "string",
                    "description": "The name of the Salesforce object (e.g., 'Account', 'Contact')",
                },
                "data": {
                    "type": "object",
                    "description": "The data for the new record",
                    "properties": {},
                    "additionalProperties": True,
                },
            },
            "required": ["object_name", "data"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Creates' implies a write/mutation operation, it doesn't mention permissions required, whether the operation is idempotent, error handling, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 just three words, front-loading the key action. Every word earns its place, with no wasted text or redundancy. This is a model of brevity for a simple tool.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after creation (e.g., returns a record ID), error conditions, or how it fits within the Salesforce context implied by the schema. More context is needed for safe and effective use.

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%, so the input schema fully documents both parameters ('object_name' and 'data'). The description adds no additional meaning beyond what's in the schema, such as examples or constraints. Baseline 3 is appropriate when the schema does all the heavy lifting for parameter 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?

The description clearly states the verb ('Creates') and resource ('a new record'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'update_record' or specify what type of record (Salesforce object) is being created, which prevents a perfect score.

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 like 'update_record' or 'delete_record'. It lacks context about prerequisites, such as needing a valid Salesforce object name, or when this operation is appropriate compared to other data manipulation tools in the sibling list.

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

Related 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/smn2gnt/MCP-Salesforce'

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