Skip to main content
Glama
Sign In
MCP Salesforce Connector

MCP Salesforce Connector

by smn2gnt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_record

Create a Salesforce record by providing the object name and the data for the new record.

Instructions

Creates a new 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>",
      "data": "<data>"
    },
    "name": "create_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe data for the new record
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

D1.3/5.0
Behavior1/5

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

With no annotations available, the description must disclose behavioral traits. It only states 'Creates a new record' without mentioning that this is a write operation, authentication requirements, potential side effects (e.g., creation of dependent records), or error conditions.

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

Conciseness1/5

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

While the description is short, it is under-specified and fails to earn its place. A single vague phrase is not concise; it omits critical information that must be inferred.

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

Completeness1/5

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

Given the complexity (nested object parameter, no output schema), the description is severely incomplete. It does not explain return values, error handling, or the behavior of the 'data' parameter. Sibling tools exist but no differentiation is provided.

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 the schema already documents both parameters. The description adds no meaning beyond the schema; it does not clarify the format of 'data' or provide examples. Baseline of 3 is appropriate since the schema is self-sufficient.

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

Purpose1/5

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

The description 'Creates a new record' is a tautology that simply restates the tool name 'create_record' without specifying the target system (Salesforce) or distinguishing it from sibling tools like 'bulk_create_records'.

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

Usage Guidelines1/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 such as 'bulk_create_records' or 'update_record'. The description lacks any context about prerequisites or scenarios.

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