Skip to main content
Glama
Sign In
MCP_Salesforce

MCP_Salesforce

by waaljair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_contact

Update a Salesforce contact's details by specifying the contact ID and the fields to change, such as email, phone, or title.

Instructions

Update a Salesforce contact with new information

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": {
      "contactId": "<contactId>",
      "updates": "<updates>"
    },
    "name": "update_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYesFields to update on the contact
contactIdYesThe Salesforce Contact ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavior. It only says 'update with new information' but does not clarify if this is a partial update, whether unchanged fields are preserved, or what happens on invalid data. This leaves the agent guessing about side effects.

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?

The description is a single, front-loaded sentence with no filler or redundant information. Every word earns its place.

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

Completeness3/5

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

The tool is simple, and the schema covers parameters, but the description does not explain expected behavior (e.g., partial vs. full replace, error handling) or when this tool should be selected over alternatives. Given the absence of an output schema, a bit more context would be helpful, though the tool is straightforward.

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?

The input schema already documents both parameters completely (contactId and updates object). The description adds no additional meaning beyond what the schema provides, so the baseline score of 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?

The description clearly states the action ('Update') and the resource ('Salesforce contact'), making it obvious which tool to use. It distinguishes from siblings like update_account and update_opportunity by specifying the contact resource.

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?

The description provides no guidance on when to use this tool versus alternatives such as create_contact or update_account. It lacks context on prerequisites like whether the contact must already exist or how partial updates behave.

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