Skip to main content
Glama

salesforce_search_objects

Search Salesforce standard and custom objects using name patterns to quickly locate specific data structures within your Salesforce instance.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchPatternYesSearch pattern to find objects (e.g., 'Account Coverage' will find objects like 'AccountCoverage__c')

Implementation Reference

  • The handler function that executes the tool: calls conn.describeGlobal(), filters Salesforce objects by search terms in name or label, and returns formatted results or no-match message.
    export async function handleSearchObjects(conn: any, searchPattern: string) {
      // Get list of all objects
      const describeGlobal = await conn.describeGlobal();
      
      // Process search pattern to create a more flexible search
      const searchTerms = searchPattern.toLowerCase().split(' ').filter(term => term.length > 0);
      
      // Filter objects based on search pattern
      const matchingObjects = describeGlobal.sobjects.filter((obj: SalesforceObject) => {
        const objectName = obj.name.toLowerCase();
        const objectLabel = obj.label.toLowerCase();
        
        // Check if all search terms are present in either the API name or label
        return searchTerms.every(term => 
          objectName.includes(term) || objectLabel.includes(term)
        );
      });
    
      if (matchingObjects.length === 0) {
        return {
          content: [{
            type: "text",
            text: `No Salesforce objects found matching "${searchPattern}".`
          }],
          isError: false,
        };
      }
    
      // Format the output
      const formattedResults = matchingObjects.map((obj: SalesforceObject) => 
        `${obj.name}${obj.custom ? ' (Custom)' : ''}\n  Label: ${obj.label}`
      ).join('\n\n');
    
      return {
        content: [{
          type: "text",
          text: `Found ${matchingObjects.length} matching objects:\n\n${formattedResults}`
        }],
        isError: false,
      };
    }
  • Tool schema definition including name, description, and inputSchema specifying the required 'searchPattern' parameter.
    export const SEARCH_OBJECTS: Tool = {
      name: "salesforce_search_objects",
      description: "Search for Salesforce standard and custom objects by name pattern. Examples: 'Account' will find Account, AccountHistory; 'Order' will find WorkOrder, ServiceOrder__c etc.",
      inputSchema: {
        type: "object",
        properties: {
          searchPattern: {
            type: "string",
            description: "Search pattern to find objects (e.g., 'Account Coverage' will find objects like 'AccountCoverage__c')"
          }
        },
        required: ["searchPattern"]
      }
    };
  • src/index.ts:55-59 (registration)
    Registration/dispatch: Switch case in CallToolRequestSchema handler that validates arguments and calls the handleSearchObjects function.
    case "salesforce_search_objects": {
      const { searchPattern } = args as { searchPattern: string };
      if (!searchPattern) throw new Error('searchPattern is required');
      return await handleSearchObjects(conn, searchPattern);
    }
  • src/index.ts:35-45 (registration)
    Tool registration: Includes SEARCH_OBJECTS in the list of tools returned by ListToolsRequestSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        SEARCH_OBJECTS, 
        DESCRIBE_OBJECT, 
        QUERY_RECORDS, 
        DML_RECORDS,
        MANAGE_OBJECT,
        MANAGE_FIELD,
        SEARCH_ALL
      ],
    }));
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the search functionality. It does not disclose behavioral traits such as permissions needed, rate limits, pagination, or what happens on no matches. This is a significant gap for a search tool with zero annotation coverage.

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 front-loaded with the core purpose, followed by illustrative examples. Every sentence earns its place by clarifying the tool's behavior without redundancy. It is appropriately sized and efficient.

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?

Given no annotations and no output schema, the description is adequate for a simple search tool but incomplete. It explains what the tool does but lacks details on return values, error handling, or advanced usage. It meets minimum viability but has clear gaps.

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 schema already documents the 'searchPattern' parameter. The description adds value with examples ('Account' vs 'Account Coverage'), but does not provide additional syntax or format details beyond what the schema implies. Baseline 3 is 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 clearly states the specific action ('Search for Salesforce standard and custom objects') and resource ('by name pattern'), distinguishing it from siblings like 'salesforce_describe_object' (describe single object) and 'salesforce_search_all' (search records). The examples reinforce the scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context through examples (e.g., finding 'Account' vs 'AccountHistory'), but does not explicitly state when to use this tool versus alternatives like 'salesforce_search_all' or 'salesforce_query_records'. It provides clear intent but lacks explicit comparison.

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/SurajAdsul/mcp-server-salesforce'

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