mcp-server-salesforce

salesforce_search_objects

Read-only

Search Salesforce standard and custom objects by entering a name pattern. Returns matching object names to help locate the right object for queries and data management.

Instructions

Search for Salesforce standard and custom objects by name pattern. Examples: 'Account' will find Account, AccountHistory; 'Order' will find WorkOrder, ServiceOrder__c etc.

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": {
      "searchPattern": "<searchPattern>"
    },
    "name": "salesforce_search_objects"
  }
}

Input Schema

Name	Required	Description	Default
`searchPattern`	Yes	Search pattern to find objects (e.g., 'Account Coverage' will find objects like 'AccountCoverage__c')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.7Sep 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries the behavioral disclosure burden. It adds meaningful detail about partial-pattern matching and inclusion of custom objects, helping an agent predict that a search may return multiple related object definitions.

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 sentences deliver the core operation first, followed by concrete illustrative examples. There is no filler, repetition of schema fields, or unnecessary detail.

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?

For a single-parameter read-only search tool with no output schema, the description sufficiently explains scope and matching behavior to support correct invocation. It could be slightly stronger by describing the return shape, but that is not essential here.

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 description coverage is 100%, so the baseline of 3 applies. The tool description reinforces pattern-matching behavior with examples, but the parameter meaning is already fully conveyed by the schema.

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?

States a specific verb ('Search'), a specific resource ('Salesforce standard and custom objects'), and a matching criterion ('by name pattern'). The examples make it clear this returns object definitions rather than records, distinguishing it from salesforce_search_all and salesforce_describe_object.

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 explains what the tool does but gives no guidance on when to use it versus alternatives such as salesforce_search_all or salesforce_describe_object. There are no explicit conditions, exclusions, or recommended usage contexts.

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

Deploy Server