Skip to main content
Glama

run_sosl_search

Execute SOSL searches to find records across multiple Salesforce objects and fields using structured queries.

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

  • Executes the SOSL search tool logic: extracts 'search' argument, performs sf_client.sf.search(), and returns JSON results 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)}",
            )
        ]
  • Tool registration in handle_list_tools(): defines name, description, and inputSchema for 'run_sosl_search' 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('executes') but doesn't mention critical details like authentication requirements, rate limits, error handling, or what the output looks like (e.g., search results format). This leaves significant gaps for a tool that performs searches.

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, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete for a search tool. It doesn't explain what the tool returns (e.g., search results, error messages) or behavioral aspects like permissions or limits, which are crucial for an agent to use it effectively in Salesforce contexts.

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 'search' parameter well-documented in the schema itself. The description doesn't add any extra meaning about parameters beyond what's in the schema, so it meets the baseline of 3 for high schema coverage without compensating 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 verb ('executes') and resource ('SOSL search against Salesforce'), making the purpose understandable. However, it doesn't differentiate this tool from its sibling 'run_soql_query', which also executes searches in Salesforce, leaving some ambiguity about when to use SOSL versus SOQL.

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?

No guidance is provided on when to use this tool versus alternatives. With sibling tools like 'run_soql_query' and 'restful' available, the description lacks any context about SOSL's specific use cases, prerequisites, or comparisons to other search methods, leaving the agent without usage direction.

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

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/leilaabdel/MCP-Salesforce'

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