Skip to main content
Glama
jonathan-politzki

Smartlead Simplified MCP Server

smartlead_fetch_webhooks_by_campaign

Retrieve all webhooks configured for a specific email marketing campaign by providing the campaign ID.

Instructions

Fetch all the webhooks associated with a campaign using the campaign ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesID of the campaign to fetch webhooks for

Implementation Reference

  • The core handler function that validates input using isFetchWebhooksByCampaignParams, creates a SmartLead API client, makes a GET request to `/campaigns/${campaign_id}/webhooks` with retry logic, and returns the response data or error.
    async function handleFetchWebhooksByCampaign(
      args: unknown,
      apiClient: AxiosInstance,
      withRetry: <T>(operation: () => Promise<T>, context: string) => Promise<T>
    ) {
      if (!isFetchWebhooksByCampaignParams(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Invalid arguments for smartlead_fetch_webhooks_by_campaign'
        );
      }
    
      try {
        const smartLeadClient = createSmartLeadClient(apiClient);
        const { campaign_id } = args;
        
        const response = await withRetry(
          async () => smartLeadClient.get(`/campaigns/${campaign_id}/webhooks`),
          'fetch webhooks by campaign'
        );
    
        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,
        };
      }
    }
  • Defines the tool metadata: name, description, ToolCategory.WEBHOOKS, and input schema requiring 'campaign_id' string.
    export const FETCH_WEBHOOKS_BY_CAMPAIGN_TOOL: CategoryTool = {
      name: 'smartlead_fetch_webhooks_by_campaign',
      description: 'Fetch all the webhooks associated with a campaign using the campaign ID.',
      category: ToolCategory.WEBHOOKS,
      inputSchema: {
        type: 'object',
        properties: {
          campaign_id: {
            type: 'string',
            description: 'ID of the campaign to fetch webhooks for',
          },
        },
        required: ['campaign_id'],
      },
    };
  • src/index.ts:221-224 (registration)
    Conditionally registers all webhook tools (including smartlead_fetch_webhooks_by_campaign) via toolRegistry.registerMany(webhookTools) if webhooks category is enabled.
    // Register webhook tools if enabled
    if (enabledCategories.webhooks) {
      toolRegistry.registerMany(webhookTools);
    }
  • Runtime type guard for validating input arguments match FetchWebhooksByCampaignParams interface (campaign_id: string), used in the handler.
    export function isFetchWebhooksByCampaignParams(args: unknown): args is FetchWebhooksByCampaignParams {
      return (
        typeof args === 'object' &&
        args !== null &&
        'campaign_id' in args &&
        typeof (args as FetchWebhooksByCampaignParams).campaign_id === 'string'
      );
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but lacks details on permissions required, rate limits, pagination, or the format of returned webhooks. This is inadequate for a tool that fetches data, as it leaves key operational traits unspecified.

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 unnecessary words. It is front-loaded and appropriately sized, 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 what the returned webhooks look like, potential error conditions, or how to handle multiple webhooks. For a fetch operation with no structured output, more context is needed to guide effective use.

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 schema description coverage is 100%, so the input schema already documents the single parameter 'campaign_id' with its description. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, meeting the baseline for high schema coverage.

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 ('Fetch') and resource ('webhooks associated with a campaign'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'smartlead_get_webhooks_publish_summary' or 'smartlead_upsert_campaign_webhook', which might handle webhooks differently, so it misses full sibling differentiation.

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, such as needing an existing campaign ID, or compare it to other webhook-related tools in the sibling list, leaving usage context implied at best.

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