Skip to main content
Glama
jonathan-politzki

Smartlead Simplified MCP Server

smartlead_search_domain

Search for available domains under $15 that match a specific name pattern using Smartlead's vendor system to find affordable domain options.

Instructions

Search for available domains under $15 that match a given domain name pattern.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domain_nameYesThe domain name pattern you want to search for
vendor_idYesID of the vendor from whom you want to purchase the domain (use Get Vendors API to retrieve this ID)

Implementation Reference

  • Entry point for executing smartlead_search_domain and other SMART_SENDERS category tools; dispatches to specific handleSmartSendersTool function.
    case ToolCategory.SMART_SENDERS:
      return await handleSmartSendersTool(name, toolArgs, apiClient, withRetry);
  • Primary schema definition for the smartlead_search_domain tool, including name, description, category, and detailed input schema.
    export const SEARCH_DOMAIN_TOOL: CategoryTool = {
      name: 'smartlead_search_domain',
      description: 'Search for available domains under $15 that match a given domain name pattern.',
      category: ToolCategory.SMART_SENDERS,
      inputSchema: {
        type: 'object',
        properties: {
          domain_name: {
            type: 'string',
            description: 'The domain name pattern you want to search for',
          },
          vendor_id: {
            type: 'integer',
            description: 'ID of the vendor from whom you want to purchase the domain (use Get Vendors API to retrieve this ID)',
          },
        },
        required: ['domain_name', 'vendor_id'],
      },
    };
  • src/index.ts:233-234 (registration)
    Registers the array of SmartSenders tools (including smartlead_search_domain) to the tool registry if the feature is enabled.
      toolRegistry.registerMany(smartSendersTools);
    }
  • TypeScript interface defining the expected input parameters for the smartlead_search_domain tool.
    export interface SearchDomainParams {
      domain_name: string;
      vendor_id: number;
    }
  • Type guard helper function for validating input arguments match SearchDomainParams for the smartlead_search_domain tool.
    export function isSearchDomainParams(args: unknown): args is SearchDomainParams {
      if (typeof args !== 'object' || args === null) return false;
      
      const params = args as Partial<SearchDomainParams>;
      
      return (
        typeof params.domain_name === 'string' &&
        typeof params.vendor_id === 'number'
      );
    }
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 lacks critical behavioral details. It doesn't disclose whether this is a read-only operation, what happens when domains are found (e.g., are they reserved?), rate limits, authentication requirements, or what the response format looks like. The price constraint ('under $15') is useful but insufficient for a tool with no 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 a single, efficient sentence that front-loads the core purpose. Every word earns its place - 'search,' 'available domains,' 'under $15,' and 'match a pattern' all contribute essential information without redundancy.

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?

For a tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the search returns (list of domains? availability status? pricing?), error conditions, or behavioral constraints. The price threshold is helpful but doesn't compensate for missing critical operational context.

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 both parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it mentions domain pattern and vendor but provides no extra context about format, validation, or vendor selection strategy.

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 available domains') and resource ('domains under $15'), with explicit constraints ('match a given domain name pattern'). It distinguishes this tool from sibling tools like 'smartlead_get_domain_list' (which likely lists existing domains) by focusing on searching for purchasable domains under a price threshold.

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 when looking for purchasable domains under $15, but provides no explicit guidance on when to use this versus alternatives like 'smartlead_get_domain_list' or prerequisites. It mentions a vendor_id parameter but doesn't explain when different vendors should be selected.

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