salesforce-mcp-jsforce

salesforce_update_record

Update fields on an existing Salesforce record by providing the object API name, record ID, and a field-value map.

Instructions

Update fields on an existing record.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "object_name": "<object_name>",
      "record_id": "<record_id>",
      "data": "<data>"
    },
    "name": "salesforce_update_record"
  }
}

Input Schema

Name	Required	Description
`data`	Yes	Field API name → new value map
`_sfAuth`	No	Internal: per-request Salesforce credentials injected by an MCP gateway. Leave unset in direct use — the server falls back to env/token-file creds.
`record_id`	Yes	The Id of the record to update
`object_name`	Yes	API name of the object

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Jun 19, 2026

addedInput schema / properties / _sfAuth

Added value: +{
+  "additionalProperties": false,
+  "description": "Internal: per-request Salesforce credentials injected by an MCP gateway. Leave unset in direct use — the server falls back to env/token-file creds.",
+  "properties": {
+    "accessToken": {
+      "type": "string"
+    },
+    "apiVersion": {
+      "type": "string"
+    },
+    "instanceUrl": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "accessToken",
+    "instanceUrl"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jun 19, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether partial updates are allowed, return value after update, or any side effects; the minimal description fails to compensate for the lack of annotations.

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

Conciseness4/5

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

The description is a single concise sentence with no wasted words, but it lacks additional detail that could improve clarity without adding verbosity.

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 no output schema and no annotations, the description does not explain return values, error conditions, or authentication details beyond the schema; the tool has moderately complex parameters (including nested _sfAuth), requiring more complete context.

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 schema already documents all parameters; the description adds no new meaning beyond what is in the schema, but baseline 3 is appropriate given high coverage.

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 'Update fields on an existing record' uses a specific verb (Update) and resource (fields on an existing record), clearly distinguishing it from sibling tools like create, delete, or query.

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 salesforce_create_record or salesforce_query; no when-not or exclusion criteria are mentioned.

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

Deploy Server