simple-salesforce-mcp

delete_record

DestructiveIdempotent

Permanently delete a Salesforce record after user approval. Provide the object type, record ID, and confirm=true to complete the deletion.

Instructions

Permanently delete a Salesforce record. Requires confirm=true: first present the deletion to the user and get their approval.

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_type": "<object_type>",
      "record_id": "<record_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_record"
  }
}

Input Schema

Name	Required	Description
`confirm`	Yes	Must be literally true. Before setting it, show the user the exact record and field changes and get their approval.
`record_id`	Yes	15- or 18-character Salesforce record Id.
`object_type`	Yes	Object API name, e.g. Account, Contact, or My_Object__c.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark the tool as destructive, and the description adds meaningful context: the deletion is permanent and user confirmation must precede execution. This goes beyond the structured annotations by specifying the required confirmation workflow.

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?

Two tight sentences with no filler: the first states the core action and permanence, the second gives the essential safety condition. The most important information is front-loaded.

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

Completeness4/5

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

For a destructive three-parameter tool, the description, annotations, and schema together cover the operation, required confirmation, parameter formats, and irreversibility. No output schema exists, but explaining a delete return value is not essential for correct invocation.

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%, and the schema already documents each parameter in detail, including the confirm requirement and the need to show the user the exact record. The description mostly restates the confirm policy rather than adding new parameter-level meaning.

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 uses a specific verb ('delete'), names the resource ('Salesforce record'), and adds the critical qualifier 'permanently'. This clearly distinguishes it from the sibling tools create_record, update_record, get_record, and search_records.

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

Usage Guidelines4/5

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

The description gives explicit operational guidance: confirm=true is required and user approval must be obtained before proceeding. It doesn't explicitly name alternatives, but the delete intent is self-evident and the confirmation gate is the key usage condition.

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

Deploy Server