Skip to main content
Glama
Sign In
MCP Salesforce Connector

MCP Salesforce Connector

by smn2gnt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_record

Delete a record from Salesforce by specifying the object name and record ID.

Instructions

Deletes a record

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": "delete_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
record_idYesThe ID of the record to delete
object_nameYesThe name of the Salesforce object (e.g., 'Account', 'Contact')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states the action 'deletes'. It fails to disclose irreversibility, required permissions, or side effects, which are critical for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (3 words), sacrificing necessary behavioral and usage details. This is under-specification, not good conciseness.

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 the simple 2-parameter tool and no output schema, the description should at least differentiate from sibling tools and indicate scope (single record, Salesforce context). It fails to do so.

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?

Parameter meanings are fully covered by the schema (100% coverage). The description adds no extra context, but baseline score is 3 due to complete schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Deletes a record' is a tautology that adds no new information beyond the tool name. It does not differentiate from sibling tools like bulk_delete_records, which also delete records.

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 versus alternatives (e.g., bulk_delete_records for multiple records). The description implies single-record deletion but does not state it explicitly or mention prerequisites.

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

Deploy Server

Other Tools