Skip to main content
Glama
jonathan-politzki

Smartlead Simplified MCP Server

smartlead_get_ip_details

Retrieve IP blacklist details for specific email campaigns to identify deliverability issues and monitor sender reputation.

Instructions

Get the list of all blacklists per IP for a specific email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reply_idYesID of the email received by the seed account
spam_test_idYesID of the spam test

Implementation Reference

  • The core handler function that validates input using isIpDetailsParams, creates a SmartDelivery API client, makes a GET request to retrieve IP details for the specified spam_test_id and reply_id, and returns the JSON response or error.
    async function handleGetIpDetails(
      args: unknown, 
      apiClient: AxiosInstance,
      withRetry: <T>(operation: () => Promise<T>, context: string) => Promise<T>
    ) {
      if (!isIpDetailsParams(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Invalid arguments for smartlead_get_ip_details'
        );
      }
    
      try {
        const smartDeliveryClient = createSmartDeliveryClient(apiClient);
        const { spam_test_id, reply_id } = args;
        
        const response = await withRetry(
          async () => smartDeliveryClient.get(`/spam-test/report/${spam_test_id}/sender-account-wise/${reply_id}/ip-details`),
          'get IP details'
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
          isError: false,
        };
      } catch (error: any) {
        return {
          content: [{ 
            type: 'text', 
            text: `API Error: ${error.response?.data?.message || error.message}` 
          }],
          isError: true,
        };
      }
    }
  • Tool schema definition with input validation requiring spam_test_id and reply_id integers.
    export const GET_IP_DETAILS_TOOL: CategoryTool = {
      name: 'smartlead_get_ip_details',
      description: 'Get the list of all blacklists per IP for a specific email.',
      category: ToolCategory.SMART_DELIVERY,
      inputSchema: {
        type: 'object',
        properties: {
          spam_test_id: {
            type: 'integer',
            description: 'ID of the spam test',
          },
          reply_id: {
            type: 'integer',
            description: 'ID of the email received by the seed account',
          },
        },
        required: ['spam_test_id', 'reply_id'],
      },
    };
  • src/index.ts:217-219 (registration)
    Registration of all smartDeliveryTools (including smartlead_get_ip_details) to the toolRegistry if smartDelivery category is enabled.
    if (enabledCategories.smartDelivery) {
      toolRegistry.registerMany(smartDeliveryTools);
    }
  • Dispatcher switch case that routes 'smartlead_get_ip_details' calls to the specific handleGetIpDetails function.
    case 'smartlead_get_ip_details': {
      return handleGetIpDetails(args, apiClient, withRetry);
    }
  • src/index.ts:354-355 (registration)
    Main tool call dispatcher in index.ts that routes SMART_DELIVERY category tools to handleSmartDeliveryTool.
    case ToolCategory.SMART_DELIVERY:
      return await handleSmartDeliveryTool(name, toolArgs, apiClient, withRetry);
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 the tool retrieves a list of blacklists per IP, implying a read-only operation, but doesn't cover critical aspects like authentication needs, rate limits, error handling, or what the output format looks like (e.g., JSON structure, pagination). This leaves significant gaps for an AI agent to understand how to invoke it effectively.

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 fluff or redundancy. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 the return values, error conditions, or behavioral traits like side effects or performance considerations. For a tool with two required parameters and no structured output documentation, more context is needed to ensure reliable use by an AI agent.

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, with clear documentation for both parameters ('reply_id' and 'spam_test_id'). The description doesn't add any additional meaning beyond what the schema provides, such as explaining the relationship between these IDs or usage examples. Since schema coverage is high, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 ('Get the list of all blacklists per IP') and the target resource ('for a specific email'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'smartlead_get_blacklist' or 'smartlead_get_spam_filter_details', which might have overlapping functionality related to blacklists or spam testing.

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, and with many sibling tools (e.g., 'smartlead_get_blacklist', 'smartlead_get_spam_test_details'), there's no indication of how this tool differs or when it's preferred.

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