salesforce-mcp

update_record

Modify existing Salesforce records by providing object name, record ID, and updated data fields to maintain accurate information.

Instructions

Updates an existing record

Input Schema

TableJSON Schema

Name	Required	Description
`object_name`	Yes	The name of the Salesforce object (e.g., 'Account', 'Contact')
`record_id`	Yes	The ID of the record to update
`data`	Yes	The updated data for the record

Implementation Reference

src/salesforce/server.py:373-388 (handler)

Handler implementation for the 'update_record' tool. Extracts object_name, record_id, and data from arguments, validates them, retrieves the Salesforce object dynamically, calls the update method on the record, and returns a TextContent with the result.

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}",
        )
    ]

src/salesforce/server.py:176-199 (schema)

JSON Schema definition for the 'update_record' tool inputs, specifying required parameters: object_name, record_id, and data (object). Part of the tool registration in list_tools().

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"],
    },
),

src/salesforce/server.py:176-199 (registration)

Registration of the 'update_record' tool within the @server.list_tools() decorator, including name, description, and input schema.

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"],
    },
),

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Updates', which implies mutation, but omits details like idempotency, return values, permissions, or error handling. This is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence of four words, which is concise but too terse. Given the tool has three parameters and a nested object, more context is needed. It sacrifices informativeness for brevity.

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?

With no output schema and multiple sibling tools, the description lacks essential context. It does not mention return values, error scenarios, or the relationship to other tools like 'bulk_update_records' or 'apex_execute'. The update behavior is under-specified.

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 input schema describes all three parameters with 100% coverage. However, the description adds no value beyond the schema; for the 'data' nested object, it only says 'The updated data for the record' without clarifying structure or constraints.

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 'Updates an existing record' clearly states the action and resource. It is distinct from sibling tools like 'create_record' (creates new) and 'delete_record' (deletes), making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when modifying an existing record by ID, but lacks explicit guidance on when not to use (e.g., for bulk operations or if record doesn't exist). No alternatives are mentioned despite many sibling tools.

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

Deploy Server