Skip to main content
Glama

get_campaign_metrics

Retrieve specific performance metrics for Klaviyo email campaigns, including open rates, click rates, and delivery statistics, within defined date ranges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the campaign to retrieve metrics for
metricsNoSpecific metrics to retrieve (e.g., ['open_rate', 'click_rate', 'delivered', 'bounce_rate'])
start_dateNoStart date for metrics (ISO format)
end_dateNoEnd date for metrics (ISO format)
conversion_metric_idNoID of the metric to use for conversion statistics

Implementation Reference

  • The handler function that executes the get_campaign_metrics tool. It constructs a payload for the Klaviyo /campaign-values-reports/ endpoint, handles timeframe and statistics validation, includes fallback logic, and returns formatted results or error.
    async (params) => {
      try {
        logger.info(`Retrieving campaign metrics for campaign ID: ${params.id}`);
    
        // Prepare statistics list with valid names
        const statistics = params.metrics || DEFAULT_STATISTICS.standard;
    
        // Validate statistics to ensure they're supported by the API
        const validatedStatistics = statistics.filter(stat => VALID_CAMPAIGN_STATISTICS.includes(stat));
    
        if (validatedStatistics.length === 0) {
          logger.warn(`No valid statistics provided for campaign metrics. Using default: ${DEFAULT_STATISTICS.basic}`);
          validatedStatistics.push(...DEFAULT_STATISTICS.basic);
        }
    
        // Create payload for the reporting API
        const payload = {
          data: {
            type: "campaign-values-report",
            attributes: {
              statistics: validatedStatistics,
              filter: FILTER_TEMPLATES.campaignId(params.id),
              conversion_metric_id: params.conversion_metric_id || API_CONFIG.defaultConversionMetricId
            }
          }
        };
    
        // Add timeframe - either predefined or custom dates
        if (params.start_date && params.end_date) {
          payload.data.attributes.timeframe = {
            start: params.start_date,
            end: params.end_date
          };
          logger.debug(`Using custom timeframe: ${params.start_date} to ${params.end_date}`);
        } else {
          // Default to last 30 days
          payload.data.attributes.timeframe = {
            key: API_CONFIG.defaultTimeframe
          };
          logger.debug(`Using default timeframe: ${API_CONFIG.defaultTimeframe}`);
        }
    
        logger.debug('Campaign metrics request payload', payload);
    
        // Define the fallback function
        const fallbackFn = async (error) => {
          logger.warn(`Error retrieving campaign metrics with initial parameters: ${error.message}. Attempting fallback.`);
          
          // Fallback to minimal statistics set
          const fallbackPayload = {
            data: {
              type: "campaign-values-report",
              attributes: {
                statistics: DEFAULT_STATISTICS.basic,
                timeframe: {
                  key: API_CONFIG.defaultTimeframe
                },
                conversion_metric_id: API_CONFIG.defaultConversionMetricId,
                filter: FILTER_TEMPLATES.campaignId(params.id)
              }
            }
          };
    
          logger.debug('Campaign metrics fallback payload', fallbackPayload);
          
          const fallbackResults = await klaviyoClient.post('/campaign-values-reports/', fallbackPayload);
          logger.info(`Successfully retrieved basic campaign metrics for campaign ID: ${params.id} using fallback`);
          
          return fallbackResults;
        };
    
        // Use the post method with the fallback function
        const results = await klaviyoClient.post('/campaign-values-reports/', payload, fallbackFn);
    
        logger.info(`Successfully retrieved campaign metrics for campaign ID: ${params.id}`);
    
        return {
          content: [{ type: "text", text: JSON.stringify(results, null, 2) }]
        };
      } catch (error) {
        logger.error(`Failed to retrieve campaign metrics (including fallback attempt): ${error.message}`, {
          campaignId: params.id
        });
    
        return {
          content: [{ type: "text", text: `Error retrieving campaign metrics (including fallback attempt): ${error.message}` }],
          isError: true
        };
      }
    },
  • Zod schema defining the input parameters for the get_campaign_metrics tool: campaign ID (required), optional metrics list, date range, and conversion metric ID.
    {
      id: z.string().describe("ID of the campaign to retrieve metrics for"),
      metrics: z.array(z.string()).optional().describe("Specific metrics to retrieve (e.g., ['open_rate', 'click_rate', 'delivered', 'bounce_rate'])"),
      start_date: z.string().optional().describe("Start date for metrics (ISO format)"),
      end_date: z.string().optional().describe("End date for metrics (ISO format)"),
      conversion_metric_id: z.string().optional().describe("ID of the metric to use for conversion statistics")
    },
  • Direct registration of the get_campaign_metrics tool using server.tool within the registerReportingTools function.
    server.tool(
      "get_campaign_metrics",
      {
        id: z.string().describe("ID of the campaign to retrieve metrics for"),
        metrics: z.array(z.string()).optional().describe("Specific metrics to retrieve (e.g., ['open_rate', 'click_rate', 'delivered', 'bounce_rate'])"),
        start_date: z.string().optional().describe("Start date for metrics (ISO format)"),
        end_date: z.string().optional().describe("End date for metrics (ISO format)"),
        conversion_metric_id: z.string().optional().describe("ID of the metric to use for conversion statistics")
      },
      async (params) => {
        try {
          logger.info(`Retrieving campaign metrics for campaign ID: ${params.id}`);
    
          // Prepare statistics list with valid names
          const statistics = params.metrics || DEFAULT_STATISTICS.standard;
    
          // Validate statistics to ensure they're supported by the API
          const validatedStatistics = statistics.filter(stat => VALID_CAMPAIGN_STATISTICS.includes(stat));
    
          if (validatedStatistics.length === 0) {
            logger.warn(`No valid statistics provided for campaign metrics. Using default: ${DEFAULT_STATISTICS.basic}`);
            validatedStatistics.push(...DEFAULT_STATISTICS.basic);
          }
    
          // Create payload for the reporting API
          const payload = {
            data: {
              type: "campaign-values-report",
              attributes: {
                statistics: validatedStatistics,
                filter: FILTER_TEMPLATES.campaignId(params.id),
                conversion_metric_id: params.conversion_metric_id || API_CONFIG.defaultConversionMetricId
              }
            }
          };
    
          // Add timeframe - either predefined or custom dates
          if (params.start_date && params.end_date) {
            payload.data.attributes.timeframe = {
              start: params.start_date,
              end: params.end_date
            };
            logger.debug(`Using custom timeframe: ${params.start_date} to ${params.end_date}`);
          } else {
            // Default to last 30 days
            payload.data.attributes.timeframe = {
              key: API_CONFIG.defaultTimeframe
            };
            logger.debug(`Using default timeframe: ${API_CONFIG.defaultTimeframe}`);
          }
    
          logger.debug('Campaign metrics request payload', payload);
    
          // Define the fallback function
          const fallbackFn = async (error) => {
            logger.warn(`Error retrieving campaign metrics with initial parameters: ${error.message}. Attempting fallback.`);
            
            // Fallback to minimal statistics set
            const fallbackPayload = {
              data: {
                type: "campaign-values-report",
                attributes: {
                  statistics: DEFAULT_STATISTICS.basic,
                  timeframe: {
                    key: API_CONFIG.defaultTimeframe
                  },
                  conversion_metric_id: API_CONFIG.defaultConversionMetricId,
                  filter: FILTER_TEMPLATES.campaignId(params.id)
                }
              }
            };
    
            logger.debug('Campaign metrics fallback payload', fallbackPayload);
            
            const fallbackResults = await klaviyoClient.post('/campaign-values-reports/', fallbackPayload);
            logger.info(`Successfully retrieved basic campaign metrics for campaign ID: ${params.id} using fallback`);
            
            return fallbackResults;
          };
    
          // Use the post method with the fallback function
          const results = await klaviyoClient.post('/campaign-values-reports/', payload, fallbackFn);
    
          logger.info(`Successfully retrieved campaign metrics for campaign ID: ${params.id}`);
    
          return {
            content: [{ type: "text", text: JSON.stringify(results, null, 2) }]
          };
        } catch (error) {
          logger.error(`Failed to retrieve campaign metrics (including fallback attempt): ${error.message}`, {
            campaignId: params.id
          });
    
          return {
            content: [{ type: "text", text: `Error retrieving campaign metrics (including fallback attempt): ${error.message}` }],
            isError: true
          };
        }
      },
      { description: "Get performance metrics for a specific campaign (open rates, click rates, etc.)" }
    );
  • src/server.js:38-38 (registration)
    Invocation of registerReportingTools(server) which includes the registration of get_campaign_metrics along with other reporting tools.
    registerReportingTools(server);
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/ivan-rivera-projects/Klaviyo-MCP-Server-Enhanced'

If you have feedback or need assistance with the MCP directory API, please join our Discord server