salesforce-mcp-jsforce

salesforce_get_record

Retrieve a single Salesforce record by its 15- or 18-character ID, optionally limiting returned fields to specific API names. Specify the object name and record ID to fetch the data you need.

Instructions

Retrieve a single record by Id, optionally limited to specific fields.

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>"
    },
    "name": "salesforce_get_record"
  }
}

Input Schema

Name	Required	Description
`fields`	No	Optional list of field API names; omit for all fields
`_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 15- or 18-char record Id
`object_name`	Yes	API name of the object, e.g. Account

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.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'retrieve' (read-only implied), but doesn't disclose authentication requirements, rate limits, error handling, or what happens with invalid IDs. The _sfAuth parameter is explained in the schema but not in the description.

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?

Single, front-loaded sentence of 12 words. No fluff. Every word is necessary and informative.

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

Completeness3/5

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

For a simple retrieval tool with a well-described schema, the description is minimally adequate. However, it lacks usage guidance and behavioral context, which would help an agent decide when to invoke this tool over siblings like salesforce_query.

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 coverage is 100%, so baseline is 3. The description repeats the purpose of record_id and fields ('by Id', 'optionally limited to specific fields') but adds no new semantic meaning beyond what the schema already provides.

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 tool retrieves a single record by ID, with optional field limiting. The verb 'Retrieve' and resource 'single record' are specific, and the sibling tools include query (multiple records) and create/update/delete, so this is well differentiated.

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?

No guidance on when to use this tool versus siblings like salesforce_query or salesforce_search. The description implies use for a single record by ID, but doesn't explicitly state when not to use it or suggest alternatives.

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

Deploy Server