Skip to main content
Glama
jonathan-politzki

Smartlead Simplified MCP Server

smartlead_place_order_mailboxes

Place orders to purchase domains and associated mailboxes for email marketing campaigns, specifying vendor, forwarding domain, and mailbox details.

Instructions

Confirm and place order for domains and mailboxes to be purchased.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainsYesList of domains and associated mailbox details for purchase
forwarding_domainYesThe domain to forward to when users access purchased domains
vendor_idYesID of the vendor from whom you want to purchase the domains and mailboxes

Implementation Reference

  • Primary tool schema definition including name, description, category, and detailed input schema for validating parameters like vendor_id, forwarding_domain, and domains with mailbox_details.
    export const PLACE_ORDER_MAILBOXES_TOOL: CategoryTool = {
      name: 'smartlead_place_order_mailboxes',
      description: 'Confirm and place order for domains and mailboxes to be purchased.',
      category: ToolCategory.SMART_SENDERS,
      inputSchema: {
        type: 'object',
        properties: {
          vendor_id: {
            type: 'integer',
            description: 'ID of the vendor from whom you want to purchase the domains and mailboxes',
          },
          forwarding_domain: {
            type: 'string',
            description: 'The domain to forward to when users access purchased domains',
          },
          domains: {
            type: 'array',
            items: {
              type: 'object',
              properties: {
                domain_name: {
                  type: 'string',
                  description: 'The domain name you want to purchase',
                },
                mailbox_details: {
                  type: 'array',
                  items: {
                    type: 'object',
                    properties: {
                      mailbox: {
                        type: 'string',
                        description: 'The complete mailbox address (e.g., john@example.com)',
                      },
                      first_name: {
                        type: 'string',
                        description: 'First name for the mailbox owner',
                      },
                      last_name: {
                        type: 'string',
                        description: 'Last name for the mailbox owner',
                      },
                      profile_pic: {
                        type: 'string',
                        description: 'URL or identifier for profile picture (optional)',
                      },
                    },
                    required: ['mailbox', 'first_name', 'last_name'],
                  },
                  description: 'Details for each mailbox you want to purchase',
                },
              },
              required: ['domain_name', 'mailbox_details'],
            },
            description: 'List of domains and associated mailbox details for purchase',
          },
        },
        required: ['vendor_id', 'forwarding_domain', 'domains'],
      },
    };
  • src/index.ts:231-234 (registration)
    Registers the array of SmartSenders tools (including smartlead_place_order_mailboxes) to the central toolRegistry when the smartSenders category is enabled by feature flags.
    // Register smart senders tools if enabled
    if (enabledCategories.smartSenders) {
      toolRegistry.registerMany(smartSendersTools);
    }
  • Central request handler dispatches tool calls for SMART_SENDERS category (including smartlead_place_order_mailboxes) to the dedicated handleSmartSendersTool implementation.
    case ToolCategory.SMART_SENDERS:
      return await handleSmartSendersTool(name, toolArgs, apiClient, withRetry);
  • Groups the PLACE_ORDER_MAILBOXES_TOOL with other SmartSenders tools in an array for convenient batch registration.
    export const smartSendersTools = [
      GET_VENDORS_TOOL,
      SEARCH_DOMAIN_TOOL,
      AUTO_GENERATE_MAILBOXES_TOOL,
      PLACE_ORDER_MAILBOXES_TOOL,
      GET_DOMAIN_LIST_TOOL,
    ]; 
  • Type guard function for validating input parameters specific to the place_order_mailboxes tool, ensuring required fields like vendor_id, forwarding_domain, and mailbox details are present.
    export function isPlaceOrderParams(args: unknown): args is PlaceOrderParams {
      if (typeof args !== 'object' || args === null) return false;
      
      const params = args as Partial<PlaceOrderParams>;
      
      // Check if domains have mailbox property in mailbox_details
      const domainsHaveMailboxes = Array.isArray(params.domains) && 
        params.domains.every(domain => 
          isDomainWithMailboxes(domain) && 
          domain.mailbox_details.every(detail => typeof detail.mailbox === 'string')
        );
      
      return (
        typeof params.vendor_id === 'number' &&
        typeof params.forwarding_domain === 'string' &&
        domainsHaveMailboxes
      );
    }
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 mentions 'Confirm and place order,' implying a transactional, potentially irreversible purchase action, but fails to detail critical behaviors such as cost implications, confirmation steps, error handling, or what happens upon success/failure. This is a significant gap for a tool that likely involves financial transactions.

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 action and target resources without unnecessary words. It is front-loaded with the core purpose, making it easy to understand quickly, and every part of the sentence contributes to clarifying the tool's intent.

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 a purchase tool with no annotations and no output schema, the description is insufficient. It does not address behavioral aspects like transactional safety, cost, or confirmation processes, nor does it explain what the tool returns upon execution. For a tool that likely involves significant actions (financial purchases), more context is needed to ensure safe and correct usage.

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, clearly documenting all parameters (domains, forwarding_domain, vendor_id) and their nested structures. The description adds no additional semantic context beyond the schema, such as explaining the relationship between domains and mailboxes or the purpose of forwarding_domain. However, with high schema coverage, the baseline score of 3 is appropriate as the schema adequately covers parameter meanings.

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 ('Confirm and place order') and the resources ('domains and mailboxes to be purchased'), making the purpose evident. However, it does not explicitly differentiate this tool from sibling tools like 'smartlead_get_vendors' or 'smartlead_search_domain', which might relate to domain/mailbox operations but serve different purposes (e.g., fetching vs. purchasing).

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, such as whether it should be used after selecting a vendor from 'smartlead_get_vendors' or in conjunction with other tools. It also lacks information on prerequisites, like needing vendor details or domain availability, leaving usage context unclear.

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/jonathan-politzki/smartlead-mcp-server'

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