Skip to main content
Glama
Sign In
Salesforce MCP Server

Salesforce MCP Server

by LokiMCPUniverse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

salesforce_bulk_create

Insert multiple records into Salesforce using Bulk API 2.0, enabling high-volume data creation with configurable batch sizes.

Instructions

Insert multiple records using the Salesforce Bulk API 2.0.

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>",
      "records": "<records>"
    },
    "name": "salesforce_bulk_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNo
recordsYes
batch_sizeNo
object_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only states 'Insert multiple records' without mentioning that Bulk API 2.0 is asynchronous, returns a job ID, processes in batches, or handles partial errors. This omits critical behavioral traits that an agent would need to know to correctly use the tool.

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?

The description is a single, front-loaded sentence that immediately communicates the core action ('Insert multiple records') and the API ('Salesforce Bulk API 2.0'). It is free of fluff, though it may be too brief given the tool's complexity, earning a 4 rather than a 5.

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 moderate complexity of a bulk API operation and the total absence of annotations, the description is inadequate. It does not explain the asynchronous nature, batch size implications, return value structure, or error reporting. The output schema exists but the description still needs to provide behavioral context that it currently lacks.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no parameter-level meaning. It does not explain that 'records' must be field-value maps, what 'batch_size' controls, how 'org' selects a Salesforce org, or what format 'object_type' expects. The agent must infer all parameter semantics from the bare schema, which is insufficient for a complex bulk operation.

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 ('Insert') and resource ('multiple records') and explicitly names Salesforce Bulk API 2.0, clearly distinguishing it from sibling tools like salesforce_create_record which handles single records. The scope and primary action are unambiguous.

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

Usage Guidelines3/5

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

The phrase 'Insert multiple records' implies this tool is for bulk operations, contrasting with single-record create, but it does not provide explicit guidance on when to choose Bulk API over standard CRUD tools, nor does it mention efficiency thresholds, batching, or error handling. No alternatives are explicitly named or excluded.

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