Skip to main content
Glama

salesforce_query_records

Query Salesforce data using SOQL to retrieve records from any object, including parent-child relationships and filtered results.

Instructions

Query records from any Salesforce object using SOQL, including relationship queries.

Examples:

  1. Parent-to-child query (e.g., Account with Contacts):

    • objectName: "Account"

    • fields: ["Name", "(SELECT Id, FirstName, LastName FROM Contacts)"]

  2. Child-to-parent query (e.g., Contact with Account details):

    • objectName: "Contact"

    • fields: ["FirstName", "LastName", "Account.Name", "Account.Industry"]

  3. Multiple level query (e.g., Contact -> Account -> Owner):

    • objectName: "Contact"

    • fields: ["Name", "Account.Name", "Account.Owner.Name"]

  4. Related object filtering:

    • objectName: "Contact"

    • fields: ["Name", "Account.Name"]

    • whereClause: "Account.Industry = 'Technology'"

Note: When using relationship fields:

  • Use dot notation for parent relationships (e.g., "Account.Name")

  • Use subqueries in parentheses for child relationships (e.g., "(SELECT Id FROM Contacts)")

  • Custom relationship fields end in "__r" (e.g., "CustomObject__r.Name")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectNameYesAPI name of the object to query
fieldsYesList of fields to retrieve, including relationship fields
whereClauseNoWHERE clause, can include conditions on related objects
orderByNoORDER BY clause, can include fields from related objects
limitNoMaximum number of records to return

Implementation Reference

  • Main handler function that validates input, constructs SOQL query with relationship support, executes the query, formats results including nested relationships, and provides enhanced error handling.
    export async function handleQueryRecords(conn: any, args: QueryArgs) {
      const { objectName, fields, whereClause, orderBy, limit } = args;
    
      try {
        // Validate relationship field syntax
        const validation = validateRelationshipFields(fields);
        if (!validation.isValid) {
          return {
            content: [{
              type: "text",
              text: validation.error!
            }],
            isError: true,
          };
        }
    
        // Construct SOQL query
        let soql = `SELECT ${fields.join(', ')} FROM ${objectName}`;
        if (whereClause) soql += ` WHERE ${whereClause}`;
        if (orderBy) soql += ` ORDER BY ${orderBy}`;
        if (limit) soql += ` LIMIT ${limit}`;
    
        const result = await conn.query(soql);
        
        // Format the output
        const formattedRecords = result.records.map((record: any, index: number) => {
          const recordStr = fields.map(field => {
            // Handle special case for subqueries (child relationships)
            if (field.startsWith('(SELECT')) {
              const relationshipName = field.match(/FROM\s+(\w+)/)?.[1];
              if (!relationshipName) return `    ${field}: Invalid subquery format`;
              const childRecords = record[relationshipName];
              return `    ${relationshipName}: [${childRecords?.length || 0} records]`;
            }
            return '    ' + formatRelationshipResults(record, field);
          }).join('\n');
          return `Record ${index + 1}:\n${recordStr}`;
        }).join('\n\n');
    
        return {
          content: [{
            type: "text",
            text: `Query returned ${result.records.length} records:\n\n${formattedRecords}`
          }],
          isError: false,
        };
      } catch (error) {
        // Enhanced error handling for relationship queries
        const errorMessage = error instanceof Error ? error.message : String(error);
        let enhancedError = errorMessage;
    
        if (errorMessage.includes('INVALID_FIELD')) {
          // Try to identify which relationship field caused the error
          const fieldMatch = errorMessage.match(/(?:No such column |Invalid field: )['"]?([^'")\s]+)/);
          if (fieldMatch) {
            const invalidField = fieldMatch[1];
            if (invalidField.includes('.')) {
              enhancedError = `Invalid relationship field "${invalidField}". Please check:\n` +
                `1. The relationship name is correct\n` +
                `2. The field exists on the related object\n` +
                `3. You have access to the field\n` +
                `4. For custom relationships, ensure you're using '__r' suffix`;
            }
          }
        }
    
        return {
          content: [{
            type: "text",
            text: `Error executing query: ${enhancedError}`
          }],
          isError: true,
        };
      }
  • Tool schema definition for salesforce_query_records, including detailed description and input schema supporting SOQL with relationships.
    export const QUERY_RECORDS: Tool = {
      name: "salesforce_query_records",
      description: `Query records from any Salesforce object using SOQL, including relationship queries.
    
    Examples:
    1. Parent-to-child query (e.g., Account with Contacts):
       - objectName: "Account"
       - fields: ["Name", "(SELECT Id, FirstName, LastName FROM Contacts)"]
    
    2. Child-to-parent query (e.g., Contact with Account details):
       - objectName: "Contact"
       - fields: ["FirstName", "LastName", "Account.Name", "Account.Industry"]
    
    3. Multiple level query (e.g., Contact -> Account -> Owner):
       - objectName: "Contact"
       - fields: ["Name", "Account.Name", "Account.Owner.Name"]
    
    4. Related object filtering:
       - objectName: "Contact"
       - fields: ["Name", "Account.Name"]
       - whereClause: "Account.Industry = 'Technology'"
    
    Note: When using relationship fields:
    - Use dot notation for parent relationships (e.g., "Account.Name")
    - Use subqueries in parentheses for child relationships (e.g., "(SELECT Id FROM Contacts)")
    - Custom relationship fields end in "__r" (e.g., "CustomObject__r.Name")`,
      inputSchema: {
        type: "object",
        properties: {
          objectName: {
            type: "string",
            description: "API name of the object to query"
          },
          fields: {
            type: "array",
            items: { type: "string" },
            description: "List of fields to retrieve, including relationship fields"
          },
          whereClause: {
            type: "string",
            description: "WHERE clause, can include conditions on related objects",
            optional: true
          },
          orderBy: {
            type: "string",
            description: "ORDER BY clause, can include fields from related objects",
            optional: true
          },
          limit: {
            type: "number",
            description: "Maximum number of records to return",
            optional: true
          }
        },
        required: ["objectName", "fields"]
      }
    };
  • src/index.ts:67-81 (registration)
    Tool registration in the main switch dispatcher: validates arguments and calls the handleQueryRecords handler.
    case "salesforce_query_records": {
      const queryArgs = args as Record<string, unknown>;
      if (!queryArgs.objectName || !Array.isArray(queryArgs.fields)) {
        throw new Error('objectName and fields array are required for query');
      }
      // Type check and conversion
      const validatedArgs: QueryArgs = {
        objectName: queryArgs.objectName as string,
        fields: queryArgs.fields as string[],
        whereClause: queryArgs.whereClause as string | undefined,
        orderBy: queryArgs.orderBy as string | undefined,
        limit: queryArgs.limit as number | undefined
      };
      return await handleQueryRecords(conn, validatedArgs);
    }
  • src/index.ts:35-45 (registration)
    Registration of the tool schema (QUERY_RECORDS) in the listTools handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        SEARCH_OBJECTS, 
        DESCRIBE_OBJECT, 
        QUERY_RECORDS, 
        DML_RECORDS,
        MANAGE_OBJECT,
        MANAGE_FIELD,
        SEARCH_ALL
      ],
    }));
  • Helper function to validate relationship field syntax in SOQL queries.
    function validateRelationshipFields(fields: string[]): { isValid: boolean; error?: string } {
      for (const field of fields) {
        // Check for parent relationship syntax (dot notation)
        if (field.includes('.')) {
          const parts = field.split('.');
          // Check for empty parts
          if (parts.some(part => !part)) {
            return {
              isValid: false,
              error: `Invalid relationship field format: "${field}". Relationship fields should use proper dot notation (e.g., "Account.Name")`
            };
          }
          // Check for too many levels (Salesforce typically limits to 5)
          if (parts.length > 5) {
            return {
              isValid: false,
              error: `Relationship field "${field}" exceeds maximum depth of 5 levels`
            };
          }
        }
    
        // Check for child relationship syntax (subqueries)
        if (field.includes('SELECT') && !field.match(/^\(SELECT.*FROM.*\)$/)) {
          return {
            isValid: false,
            error: `Invalid subquery format: "${field}". Child relationship queries should be wrapped in parentheses`
          };
        }
      }
    
      return { isValid: true };
    }
Behavior3/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. It does well by specifying the query language (SOQL), relationship query capabilities, and syntax rules for custom relationships. However, it doesn't mention important behavioral aspects like pagination, rate limits, authentication requirements, error handling, or what happens when queries return large result sets. The examples are helpful but don't cover all behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded with the core purpose statement. The examples are well-organized and directly relevant to understanding the tool's capabilities. While comprehensive, some information could be more concise - the relationship syntax rules might be condensed. Every sentence earns its place by clarifying SOQL query patterns.

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 the tool's complexity (SOQL queries with relationships, 5 parameters) and the absence of both annotations and output schema, the description does a decent job but has gaps. It covers the core functionality and parameter usage well through examples, but doesn't address return format, error conditions, performance considerations, or how results are structured (especially for nested relationship queries). For a query tool with no output schema, more information about response structure would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds significant value through the four detailed examples that show how parameters work together in practice, especially for relationship queries. It clarifies dot notation for parent relationships, subqueries for child relationships, and the '__r' suffix for custom relationships - all semantic details beyond what the schema provides. However, it doesn't cover all parameters equally (orderBy and limit get less attention).

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 explicitly states 'Query records from any Salesforce object using SOQL, including relationship queries' - this is a specific verb ('Query') with clear resource ('records from any Salesforce object') and distinguishes from siblings like salesforce_dml_records (for data manipulation) and salesforce_search_all/search_objects (for search operations). The mention of SOQL and relationship queries further clarifies the technical approach.

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 provides clear context about when to use this tool (for SOQL queries with relationship support) and the examples demonstrate various query patterns. However, it doesn't explicitly state when NOT to use this tool or name specific alternatives among the sibling tools (like when to use salesforce_search_all instead). The guidance is strong but lacks explicit exclusion criteria.

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