Skip to main content
Glama
smn2gnt

MCP Salesforce Connector

by smn2gnt

run_sosl_search

Execute SOSL searches in Salesforce to retrieve records matching specific criteria. Use this tool to find data across objects and fields with a single query.

Instructions

Executes a SOSL search against Salesforce

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchYesThe SOSL search to execute (e.g., 'FIND {John Smith} IN ALL FIELDS')

Implementation Reference

  • The handler function within @server.call_tool() that processes the tool call for 'run_sosl_search'. It retrieves the 'search' argument, executes sf_client.sf.search(), formats the results as JSON, and returns it as TextContent.
    elif name == "run_sosl_search":
        search = arguments.get("search")
        if not search:
            raise ValueError("Missing 'search' argument")
    
        results = sf_client.sf.search(search)
        return [
            types.TextContent(
                type="text",
                text=f"SOSL Search Results (JSON):\n{json.dumps(results, indent=2)}",
            )
        ]
  • The registration of the 'run_sosl_search' tool in the @server.list_tools() handler, including its description and JSON inputSchema requiring a 'search' string.
    types.Tool(
        name="run_sosl_search",
        description="Executes a SOSL search against Salesforce",
        inputSchema={
            "type": "object",
            "properties": {
                "search": {
                    "type": "string",
                    "description": "The SOSL search to execute (e.g., 'FIND {John Smith} IN ALL FIELDS')",
                },
            },
            "required": ["search"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states the action ('Executes') but doesn't cover critical aspects like authentication requirements, rate limits, error handling, or what the search returns. For a tool that performs searches in a complex system like Salesforce, this leaves significant gaps in understanding its behavior.

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, direct sentence with zero wasted words. It's appropriately sized for a tool with one parameter and no complex output schema, making it easy to parse and understand at a glance.

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

Completeness2/5

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

Given the complexity of Salesforce searches and the lack of annotations and output schema, the description is insufficient. It doesn't explain what SOSL is, how it differs from SOQL, what the return format looks like, or any limitations. For a search tool in a CRM system, more context is needed to use it effectively.

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 has 100% description coverage, with the single parameter 'search' documented as 'The SOSL search to execute (e.g., 'FIND {John Smith} IN ALL FIELDS')'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without extra value.

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

Purpose4/5

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

The description clearly states the action ('Executes') and target resource ('SOSL search against Salesforce'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'run_soql_query', which appears to be a similar search operation, missing an opportunity to clarify the distinction between SOSL and SOQL searches.

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 like 'run_soql_query' or 'restful'. There's no mention of prerequisites, appropriate contexts, or exclusions, leaving the agent to infer usage based solely on the tool name and basic purpose.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smn2gnt/MCP-Salesforce'

If you have feedback or need assistance with the MCP directory API, please join our Discord server