Skip to main content
Glama
smn2gnt

MCP Salesforce Connector

by smn2gnt

update_record

Modify existing Salesforce records by specifying the object name, record ID, and updated data. Integrates with the MCP Salesforce Connector for efficient record management.

Instructions

Updates an existing record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe updated data for the record
object_nameYesThe name of the Salesforce object (e.g., 'Account', 'Contact')
record_idYesThe ID of the record to update

Implementation Reference

  • Handler for the 'update_record' tool: extracts object_name, record_id, and data from arguments, validates them and the Salesforce connection, then performs the update using simple-salesforce's sf_object.update method.
    elif name == "update_record":
        object_name = arguments.get("object_name")
        record_id = arguments.get("record_id")
        data = arguments.get("data")
        if not object_name or not record_id or not data:
            raise ValueError("Missing 'object_name', 'record_id', 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.update(record_id, data)
        return [
            types.TextContent(
                type="text",
                text=f"Update {object_name} Record Result: {results}",
            )
        ]
  • Registration of the 'update_record' tool in the list_tools decorator, including its description and JSON schema for input validation (object_name, record_id, data).
    types.Tool(
        name="update_record",
        description="Updates an existing record",
        inputSchema={
            "type": "object",
            "properties": {
                "object_name": {
                    "type": "string",
                    "description": "The name of the Salesforce object (e.g., 'Account', 'Contact')",
                },
                "record_id": {
                    "type": "string",
                    "description": "The ID of the record to update",
                },
                "data": {
                    "type": "object",
                    "description": "The updated data for the record",
                    "properties": {},
                    "additionalProperties": True,
                },
            },
            "required": ["object_name", "record_id", "data"],
        },
    ),
  • Input schema definition for the 'update_record' tool, specifying required fields: object_name (string), record_id (string), and data (object).
    inputSchema={
        "type": "object",
        "properties": {
            "object_name": {
                "type": "string",
                "description": "The name of the Salesforce object (e.g., 'Account', 'Contact')",
            },
            "record_id": {
                "type": "string",
                "description": "The ID of the record to update",
            },
            "data": {
                "type": "object",
                "description": "The updated data for the record",
                "properties": {},
                "additionalProperties": True,
            },
        },
        "required": ["object_name", "record_id", "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. It states the action ('Updates') but doesn't cover critical aspects like required permissions, whether changes are reversible, error handling, or rate limits. For a mutation tool, this lack of detail is a significant gap, though it doesn't contradict any annotations.

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 core action. There is no wasted language, making it efficient for quick understanding, though this brevity contributes to gaps in other dimensions like guidelines and transparency.

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 (a mutation operation with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what happens on success or failure, return values, or side effects, which are crucial for an agent to use it effectively in a Salesforce context with siblings like 'get_record'.

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?

The schema description coverage is 100%, with clear descriptions for all three parameters (object_name, record_id, data). The description adds no additional meaning beyond the schema, such as examples or constraints, so it meets the baseline of 3 where the schema does the heavy lifting without extra value from the description.

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

Purpose3/5

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

The description 'Updates an existing record' clearly states the verb ('Updates') and resource ('record'), making the purpose understandable. However, it lacks specificity about what type of record (e.g., Salesforce object) and doesn't distinguish it from sibling tools like 'create_record' or 'delete_record', which is a missed opportunity for differentiation.

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. It doesn't mention prerequisites (e.g., needing an existing record ID), exclusions, or comparisons to siblings like 'create_record' for new records or 'delete_record' for removal, leaving the agent to infer usage from context alone.

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