MCP_Salesforce

search_all_records

Perform a global search across all Salesforce records using SOSL to find relevant data by entering a search query.

Instructions

Search across all Salesforce records using SOSL (global search)

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": {
      "query": "<query>"
    },
    "name": "search_all_records"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results to return (default: 20)
`query`	Yes	Search query to find across all records

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It notes the use of SOSL and 'global search', which adds some context, but it does not explicitly state that the operation is read-only, nor does it explain any limitations or pagination behavior beyond the schema's limit parameter.

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, concise sentence that clearly states the purpose and method. It is front-loaded and contains no unnecessary words, making it easy to parse quickly.

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 description covers the core function but not the return format or behavior, especially given the lack of output schema and annotations. It adequately explains what it searches but leaves the exact result structure implicit.

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 fully describes both parameters (query and limit) with 100% coverage, so the description does not need to add much. It provides no additional detail about query syntax or how the limit applies, making baseline 3 appropriate.

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 ('Search') and a clear resource ('all Salesforce records'), explicitly differentiating it from sibling tools like search_accounts and search_contacts. It also specifies the method ('SOSL (global search)'), adding technical precision.

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 'across all records' implies this is for global search, but the description does not explicitly state when to use it over the per-object search tools or provide exclusions. Sibling tools are listed but not referenced, so guidance is only implied.

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

Deploy Server