Skip to main content
Glama
springwq

Kayzen Analytics MCP Server

by springwq

get_report_results

Fetch advertising campaign report results from Kayzen Analytics by providing a report ID and optional date range to analyze performance data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateNoEnd date in YYYY-MM-DD format
report_idYesID of the report to fetch results for
start_dateNoStart date in YYYY-MM-DD format

Implementation Reference

  • src/server.ts:57-89 (registration)
    Full registration of the MCP tool 'get_report_results', including input schema with Zod validation and the handler function that delegates to KayzenClient and returns formatted results or error.
    server.tool(
      "get_report_results",
      {
        report_id: z.string().describe("ID of the report to fetch results for"),
        start_date: z.string().optional().describe("Start date in YYYY-MM-DD format"),
        end_date: z.string().optional().describe("End date in YYYY-MM-DD format")
      },
      async (params: { report_id: string; start_date?: string; end_date?: string }) => {
        try {
          const result = await kayzenClient.getReportResults(
            params.report_id,
            params.start_date,
            params.end_date
          ) as ReportResultsResponse;
    
          return {
            content: [{
              type: "text",
              text: JSON.stringify(result, null, 2)
            }]
          };
        } catch (error) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          return {
            content: [{
              type: "text",
              text: `Error getting report results: ${errorMessage}`
            }],
            isError: true
          };
        }
      }
    );
  • The core handler logic for the 'get_report_results' tool: invokes KayzenClient.getReportResults with parameters and returns JSON-formatted response or error message.
    async (params: { report_id: string; start_date?: string; end_date?: string }) => {
      try {
        const result = await kayzenClient.getReportResults(
          params.report_id,
          params.start_date,
          params.end_date
        ) as ReportResultsResponse;
    
        return {
          content: [{
            type: "text",
            text: JSON.stringify(result, null, 2)
          }]
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [{
            type: "text",
            text: `Error getting report results: ${errorMessage}`
          }],
          isError: true
        };
      }
    }
  • Zod-based input schema defining parameters for the tool: report_id (required string), start_date and end_date (optional strings).
    {
      report_id: z.string().describe("ID of the report to fetch results for"),
      start_date: z.string().optional().describe("Start date in YYYY-MM-DD format"),
      end_date: z.string().optional().describe("End date in YYYY-MM-DD format")
    },
  • KayzenClient helper method that makes the actual API request to fetch report results using makeRequest, constructing query params for date filters.
    async getReportResults(reportId: string, startDate?: string, endDate?: string) {
      const params: Record<string, string> = {};
      if (startDate) params.start_date = startDate;
      if (endDate) params.end_date = endDate;
    
      return this.makeRequest('GET', `/reports/${reportId}/report_results`, params);
    }
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/springwq/kayzen-mcp'

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