Skip to main content
Glama
jonathan-politzki

Smartlead Simplified MCP Server

smartlead_get_domain_list

Retrieve all domains purchased through SmartSenders to manage email marketing infrastructure and verify domain ownership.

Instructions

Retrieve a list of all domains purchased through SmartSenders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Defines the tool schema including name, description, category, and input schema for smartlead_get_domain_list
    export const GET_DOMAIN_LIST_TOOL: CategoryTool = {
      name: 'smartlead_get_domain_list',
      description: 'Retrieve a list of all domains purchased through SmartSenders.',
      category: ToolCategory.SMART_SENDERS,
      inputSchema: {
        type: 'object',
        properties: {
          // This endpoint doesn't require specific parameters beyond the API key
          // which is handled at the API client level
        },
        required: [],
      },
    };
  • Registers the tool as part of the smartSendersTools array for batch registration
    export const smartSendersTools = [
      GET_VENDORS_TOOL,
      SEARCH_DOMAIN_TOOL,
      AUTO_GENERATE_MAILBOXES_TOOL,
      PLACE_ORDER_MAILBOXES_TOOL,
      GET_DOMAIN_LIST_TOOL,
    ]; 
  • Type definition for input parameters (empty object)
    // Get Domain List
    export interface GetDomainListParams {
      // This endpoint doesn't require specific parameters beyond the API key
      // which is handled at the API client level
    }
  • Type guard function for validating input arguments
    export function isGetDomainListParams(args: unknown): args is GetDomainListParams {
      // Since this endpoint doesn't require specific parameters beyond the API key
      // Any object is valid
      return typeof args === 'object' && args !== null;
    } 
  • src/index.ts:232-234 (registration)
    Conditional registration of all smartSenders tools including smartlead_get_domain_list into the tool registry
    if (enabledCategories.smartSenders) {
      toolRegistry.registerMany(smartSendersTools);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it retrieves a list but doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, potential rate limits, pagination behavior, or what format the list returns. The description is minimal and lacks essential operational context.

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 purpose without any unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the retrieved list contains (e.g., domain names, IDs, purchase dates), how it's formatted, or any behavioral aspects like error handling. For a tool with no structured data support, this leaves significant gaps in understanding.

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?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but with no parameters, the baseline is appropriately high as there's nothing to compensate for.

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 ('Retrieve a list') and resource ('all domains purchased through SmartSenders'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'smartlead_search_domain', which might retrieve filtered or specific domain information rather than a complete list.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention when to prefer this over 'smartlead_search_domain' or other domain-related tools, nor does it specify any prerequisites or contextual constraints for usage.

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