salesforce-mcp-jsforce

salesforce_create_record

Creates a new Salesforce record by providing the object API name and field-value pairs.

Instructions

Create a new record on the given object.

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

Input Schema

Name	Required	Description
`data`	Yes	Field API name → value map for the new record
`_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.
`object_name`	Yes	API name of the object, e.g. Contact

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

C2.9/5.0

Behavior2/5

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

No annotations are present, so the description bears full responsibility. It only states 'create' but fails to disclose what happens after creation (e.g., returns record ID?), any permissions required, or error behavior. The agent cannot infer side effects or safety profile from this text alone.

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?

A single sentence that is to the point and free of filler. However, it is so minimal that it borders on under-specification rather than concise completeness.

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?

For a create operation with no output schema, the description should at least hint at the return value (e.g., ID of created record). It does not. Also missing is any context about authentication (_sfAuth) or data validation. The description is incomplete for effective agent 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?

Input schema covers 100% of parameters with descriptions. The description adds no extra meaning beyond the schema, but that is acceptable per guidelines. Baseline 3 is appropriate.

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 action ('Create') and the resource ('new record on the given object'), distinguishing it from sibling tools like update, delete, or query. However, it lacks specificity about which objects are supported beyond 'given object'.

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 is provided on when to use this tool vs alternatives like salesforce_update_record or salesforce_query. There are no prerequisites, limitations, or scenarios mentioned.

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

Deploy Server