salesforce-mcp-jsforce

salesforce_delete_record

Delete a Salesforce record by ID. Provide the object API name and record ID to remove it from your org.

Instructions

Delete a record by Id.

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_delete_record"
  }
}

Input Schema

Name	Required	Description
`_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 delete
`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 provided, so description must convey behavioral traits. It only says 'Delete' without mentioning side effects like irreversibility, cascading deletes, or authentication requirements beyond what's in schema.

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?

Single sentence of 5 words is extremely concise. While more detail could be added, the current length is appropriate for a simple action, and the key elements are front-loaded.

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 is incomplete. It does not hint at return values, error handling, or required permissions, which are needed for a deletion operation.

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 parameters are already described. The description adds minimal meaning beyond 'by Id' for record_id; does not elaborate on object_name or _sfAuth. Baseline 3 is appropriate.

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?

Description clearly states verb 'Delete' and resource 'record', qualified by 'by Id'. It distinguishes from sibling tools like 'salesforce_get_record' or 'salesforce_update_record' by the delete action.

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 alternatives, no prerequisites or exclusions. The description lacks context such as depending on the record's existence or necessary permissions.

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

Deploy Server