mc-next-mcp-server

Overview Schema Source Related Servers Discussions Admin

Bulk delete Salesforce records

sf_bulk_delete_records

Delete Salesforce records in bulk by sObject and IDs, up to 200 per call; larger lists are split automatically. Requires MC_NEXT_ALLOW_DESTRUCTIVE=true because operation is destructive.

Instructions

Delete up to 200 records per call (DELETE /composite/sobjects?ids=...). This is destructive and is blocked unless MC_NEXT_ALLOW_DESTRUCTIVE=true. Larger inputs are split into multiple calls automatically.

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": {
      "sobject": "<sobject>",
      "ids": "<ids>"
    },
    "name": "sf_bulk_delete_records"
  }
}

Input Schema

Name	Required	Description
`ids`	Yes	Array of record Ids to delete.
`sobject`	Yes	API name of the sObject, e.g. "Account", "Contact", or "My_Object__c".
`allOrNone`	No	Roll back the entire batch if any delete fails. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 25, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description fully discloses the critical behavioral facts: the operation is destructive, it is gated behind an environment variable, it has a 200-record per-call cap, and larger inputs are transparently chunked. This is exactly the side-effect and prerequisite information an agent needs before invoking a delete tool.

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?

Three short, information-dense sentences front-load the action and limit, then give the destructive warning, then the batching behavior. No filler or repetition.

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

Completeness5/5

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

For a destructive multi-record tool with no output schema, the description covers the essential operational context: what is deleted, the per-call limit, the guard flag, and automatic handling of larger inputs. An agent has enough to decide whether to invoke it and what to expect.

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 descriptions for ids, sobject, and allOrNone are already clear and complete. The description reinforces the ids limit and batching behavior, but does not add significant new meaning beyond the schema, so the baseline 3 applies.

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?

States a specific action on a specific resource: delete up to 200 Salesforce records via the composite sobjects endpoint. The bulk scope and per-call limit distinguish it from single-record delete siblings like sf_delete_record and from bulk create/update tools.

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 clearly frames when to use the tool: for deleting batches of records up to 200 per call, with automatic splitting for larger inputs. It also flags a prerequisite (MC_NEXT_ALLOW_DESTRUCTIVE=true). It does not explicitly name alternative tools for single-record deletes, so it stops short of a 5.

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