Skip to main content
Glama

Salesforce

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Sf Update Record

sf_update_record
Idempotent

Update an existing Salesforce record by ID. Specify object type and field values to change. Returns success status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSalesforce record ID
fieldsYesField name/value pairs to update
objectYesSObject type (e.g., "Account")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError code if update failed
messageNoError message if update failed
successNoWhether record was updated successfully

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "description": "Error code if update failed",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message if update failed",
+      "type": "string"
+    },
+    "success": {
+      "description": "Whether record was updated successfully",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "fields": {
+      "AnnualRevenue": 5000000,
+      "Industry": "Finance"
+    },
+    "id": "001xx000003DHP",
+    "object": "Account"
+  },
+  {
+    "fields": {
+      "Email": "jane.doe@acme.com",
+      "Phone": "415-555-0200"
+    },
+    "id": "003xx000004TM1",
+    "object": "Contact"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate idempotent and non-destructive behavior. Description adds that it 'Returns success status', which aligns but does not provide additional context like partial update details or error handling. No contradiction with annotations.

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?

Two concise sentences, no redundant information. Efficiently conveys purpose and return value.

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

Completeness4/5

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

Simple update tool with good annotations and output schema (exists). Description covers core behavior; minor gap in not detailing success structure, but acceptable given schema.

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% with parameter descriptions. Description echoes 'Specify object type and field values', adding little beyond schema. Baseline score appropriate given high coverage.

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?

Description clearly states action ('Update'), resource ('Salesforce record'), and method ('by ID, specify object type and field values'). Distinguishes from siblings like sf_create_record and sf_delete_record by specifying update semantics.

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?

Implies usage for updating existing records, but no explicit guidance on when to use this vs. alternatives (e.g., sf_create_record for new records). Lacks when-not-to-use or prerequisite conditions.

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

All Salesforce toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources