Skip to main content
Glama
jonathan-politzki

Smartlead Simplified MCP Server

smartlead_get_vendors

Retrieve all active domain vendors and their corresponding IDs to manage email marketing infrastructure and sender domains.

Instructions

Retrieve all active domain vendors with their corresponding IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Schema definition for the smartlead_get_vendors tool, including empty input schema as parameters are handled by API client.
    export const GET_VENDORS_TOOL: CategoryTool = {
      name: 'smartlead_get_vendors',
      description: 'Retrieve all active domain vendors with their corresponding IDs.',
      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: [],
      },
    };
  • src/index.ts:231-234 (registration)
    Registration of smartSendersTools array (containing smartlead_get_vendors) into the tool registry, conditional on feature flag.
    // Register smart senders tools if enabled
    if (enabledCategories.smartSenders) {
      toolRegistry.registerMany(smartSendersTools);
    }
  • src/index.ts:360-361 (registration)
    Dispatch to category-specific handler (handleSmartSendersTool) for SMART_SENDERS tools including smartlead_get_vendors.
    case ToolCategory.SMART_SENDERS:
      return await handleSmartSendersTool(name, toolArgs, apiClient, withRetry);
  • TypeScript interface for input parameters of smartlead_get_vendors (empty object).
    // Get Vendors
    export interface GetVendorsParams {
      // 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 to smartlead_get_vendors (accepts any object).
    export function isGetVendorsParams(args: unknown): args is GetVendorsParams {
      // Since this endpoint doesn't require specific parameters beyond the API key
      // Any object is valid
      return typeof args === 'object' && args !== null;
    }
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 states 'Retrieve all active domain vendors,' implying a read-only operation, but lacks details on permissions, rate limits, pagination, or what 'active' means. This leaves significant gaps for an AI agent to understand the tool's behavior fully.

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, clear sentence with no wasted words. It front-loads the key action and resource, making it efficient and easy to parse for an AI agent.

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 has no parameters and no output schema, the description adequately covers the basic purpose. However, without annotations or output details, it lacks information on return format (e.g., list structure, vendor fields) and behavioral context, making it minimally complete but with clear gaps for practical use.

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 with 100% schema description coverage, so no parameter information is needed. The description doesn't add parameter details, which is appropriate, earning a baseline score of 4 for not introducing unnecessary complexity.

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') and target resource ('all active domain vendors with their corresponding IDs'), which is specific and informative. However, it doesn't explicitly differentiate from sibling tools like 'smartlead_get_domain_list' or 'smartlead_get_sender_accounts', which might also retrieve domain-related information, so it doesn't reach the highest score.

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. It doesn't mention prerequisites, context, or exclusions, such as whether it's for setup, reporting, or filtering purposes compared to other 'get' tools in the list.

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