Skip to main content
Glama

salesforce_manage_object

Create new custom objects or modify existing ones in Salesforce by configuring fields, relationships, and sharing settings to organize business data.

Instructions

Create new custom objects or modify existing ones in Salesforce:

  • Create: New custom objects with fields, relationships, and settings

  • Update: Modify existing object settings, labels, sharing model Examples: Create Customer_Feedback__c object, Update object sharing settings Note: Changes affect metadata and require proper permissions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesWhether to create new object or update existing
objectNameYesAPI name for the object (without __c suffix)
labelNoLabel for the object
pluralLabelNoPlural label for the object
descriptionNoDescription of the object
nameFieldLabelNoLabel for the name field
nameFieldTypeNoType of the name field
nameFieldFormatNoDisplay format for AutoNumber field (e.g., 'A-{0000}')
sharingModelNoSharing model for the object

Implementation Reference

  • The handler function that executes the tool logic: creates or updates Salesforce custom objects using the Metadata API.
    export async function handleManageObject(conn: any, args: ManageObjectArgs) {
      const { operation, objectName, label, pluralLabel, description, nameFieldLabel, nameFieldType, nameFieldFormat, sharingModel } = args;
    
      try {
        if (operation === 'create') {
          if (!label || !pluralLabel) {
            throw new Error('Label and pluralLabel are required for object creation');
          }
    
          // Prepare metadata for the new object
          const metadata = {
            fullName: `${objectName}__c`,
            label,
            pluralLabel,
            nameField: {
              label: nameFieldLabel || `${label} Name`,
              type: nameFieldType || 'Text',
              ...(nameFieldType === 'AutoNumber' && nameFieldFormat ? { displayFormat: nameFieldFormat } : {})
            },
            deploymentStatus: 'Deployed',
            sharingModel: sharingModel || 'ReadWrite'
          } as MetadataInfo;
    
          if (description) {
            metadata.description = description;
          }
    
          // Create the object using Metadata API
          const result = await conn.metadata.create('CustomObject', metadata);
    
          if (result && (Array.isArray(result) ? result[0].success : result.success)) {
            return {
              content: [{
                type: "text",
                text: `Successfully created custom object ${objectName}__c`
              }],
              isError: false,
            };
          }
        } else {
          // For update, first get existing metadata
          const existingMetadata = await conn.metadata.read('CustomObject', [`${objectName}__c`]);
          const currentMetadata = Array.isArray(existingMetadata) ? existingMetadata[0] : existingMetadata;
    
          if (!currentMetadata) {
            throw new Error(`Object ${objectName}__c not found`);
          }
    
          // Prepare update metadata
          const metadata = {
            ...currentMetadata,
            label: label || currentMetadata.label,
            pluralLabel: pluralLabel || currentMetadata.pluralLabel,
            description: description !== undefined ? description : currentMetadata.description,
            sharingModel: sharingModel || currentMetadata.sharingModel
          } as MetadataInfo;
    
          // Update the object using Metadata API
          const result = await conn.metadata.update('CustomObject', metadata);
    
          if (result && (Array.isArray(result) ? result[0].success : result.success)) {
            return {
              content: [{
                type: "text",
                text: `Successfully updated custom object ${objectName}__c`
              }],
              isError: false,
            };
          }
        }
    
        return {
          content: [{
            type: "text",
            text: `Failed to ${operation} custom object ${objectName}__c`
          }],
          isError: true,
        };
    
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Error ${operation === 'create' ? 'creating' : 'updating'} custom object: ${error instanceof Error ? error.message : String(error)}`
          }],
          isError: true,
        };
      }
    }
  • Tool definition including name, description, and input schema for validation.
    export const MANAGE_OBJECT: Tool = {
      name: "salesforce_manage_object",
      description: `Create new custom objects or modify existing ones in Salesforce:
      - Create: New custom objects with fields, relationships, and settings
      - Update: Modify existing object settings, labels, sharing model
      Examples: Create Customer_Feedback__c object, Update object sharing settings
      Note: Changes affect metadata and require proper permissions`,
      inputSchema: {
        type: "object",
        properties: {
          operation: {
            type: "string",
            enum: ["create", "update"],
            description: "Whether to create new object or update existing"
          },
          objectName: {
            type: "string",
            description: "API name for the object (without __c suffix)"
          },
          label: {
            type: "string",
            description: "Label for the object"
          },
          pluralLabel: {
            type: "string",
            description: "Plural label for the object"
          },
          description: {
            type: "string",
            description: "Description of the object",
            optional: true
          },
          nameFieldLabel: {
            type: "string",
            description: "Label for the name field",
            optional: true
          },
          nameFieldType: {
            type: "string",
            enum: ["Text", "AutoNumber"],
            description: "Type of the name field",
            optional: true
          },
          nameFieldFormat: {
            type: "string",
            description: "Display format for AutoNumber field (e.g., 'A-{0000}')",
            optional: true
          },
          sharingModel: {
            type: "string",
            enum: ["ReadWrite", "Read", "Private", "ControlledByParent"],
            description: "Sharing model for the object",
            optional: true
          }
        },
        required: ["operation", "objectName"]
      }
    };
  • src/index.ts:97-114 (registration)
    Switch case in CallToolRequest handler that validates arguments and calls the handleManageObject function.
    case "salesforce_manage_object": {
      const objectArgs = args as Record<string, unknown>;
      if (!objectArgs.operation || !objectArgs.objectName) {
        throw new Error('operation and objectName are required for object management');
      }
      const validatedArgs: ManageObjectArgs = {
        operation: objectArgs.operation as 'create' | 'update',
        objectName: objectArgs.objectName as string,
        label: objectArgs.label as string | undefined,
        pluralLabel: objectArgs.pluralLabel as string | undefined,
        description: objectArgs.description as string | undefined,
        nameFieldLabel: objectArgs.nameFieldLabel as string | undefined,
        nameFieldType: objectArgs.nameFieldType as 'Text' | 'AutoNumber' | undefined,
        nameFieldFormat: objectArgs.nameFieldFormat as string | undefined,
        sharingModel: objectArgs.sharingModel as 'ReadWrite' | 'Read' | 'Private' | 'ControlledByParent' | undefined
      };
      return await handleManageObject(conn, validatedArgs);
    }
  • src/index.ts:35-45 (registration)
    Registration of the tool in the ListToolsRequest handler, including MANAGE_OBJECT in the tools list.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        SEARCH_OBJECTS, 
        DESCRIBE_OBJECT, 
        QUERY_RECORDS, 
        DML_RECORDS,
        MANAGE_OBJECT,
        MANAGE_FIELD,
        SEARCH_ALL
      ],
    }));
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: 'Changes affect metadata' (important for Salesforce administrators) and 'require proper permissions' (security context). However, it doesn't mention potential side effects, rate limits, or what happens when creating/updating fails. The description doesn't contradict annotations since none exist.

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 with 4 sentences: purpose statement, bullet points for create/update operations, examples, and important note. It's front-loaded with the core purpose. Minor improvement could be merging the bullet points into the first sentence for even tighter structure.

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?

For a metadata mutation tool with 9 parameters, no annotations, and no output schema, the description provides adequate but incomplete context. It covers the core purpose, examples, and permission requirements, but lacks information about return values, error conditions, or detailed behavioral expectations. The 100% schema coverage helps, but more behavioral context would be beneficial.

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 all 9 parameters thoroughly. The description adds minimal value beyond the schema - it mentions 'fields, relationships, and settings' for create operations and 'settings, labels, sharing model' for updates, but doesn't provide additional semantic context beyond what's in the parameter descriptions. Baseline 3 is appropriate when schema does the heavy lifting.

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 tool's purpose: 'Create new custom objects or modify existing ones in Salesforce' with specific verbs (create/update) and resources (custom objects). It distinguishes from siblings like salesforce_manage_field (fields vs objects) and salesforce_describe_object (read vs write).

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 description implies usage context through examples ('Create Customer_Feedback__c object, Update object sharing settings') and mentions permissions, but doesn't explicitly state when to use this tool versus alternatives like salesforce_manage_field or salesforce_dml_records. No explicit exclusions or alternative recommendations are provided.

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