Skip to main content
Glama
ruchernchong

mcp-server-google-analytics

by ruchernchong

getEvents

Retrieve Google Analytics 4 event metrics for a specified date range to analyze user interactions and track performance.

Instructions

Get event metrics for a specific date range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateYesStart date in YYYY-MM-DD format
endDateYesEnd date in YYYY-MM-DD format
eventNameNoSpecific event name to filter by (optional)

Implementation Reference

  • Handler for the getEvents tool: destructures arguments, validates date range, and calls fetchAnalyticsData with eventName, date dimensions and eventCount metric, optionally filtering by specific eventName.
    case "getEvents": {
      const { startDate, endDate, eventName } = args as {
        startDate: string;
        endDate: string;
        eventName?: string;
      };
    
      validateDateRange(startDate, endDate);
    
      return fetchAnalyticsData({
        dateRanges: [{ startDate, endDate }],
        dimensions: [{ name: "eventName" }, { name: "date" }],
        metrics: [{ name: "eventCount" }],
        ...(eventName && {
          dimensionFilter: {
            filter: {
              fieldName: "eventName",
              stringFilter: { value: eventName },
            },
          },
        }),
      });
    }
  • Schema definition for the getEvents tool, including input parameters: startDate, endDate (required), and optional eventName.
      name: "getEvents",
      description: "Get event metrics for a specific date range",
      inputSchema: {
        type: "object",
        properties: {
          startDate: {
            type: "string",
            description: "Start date in YYYY-MM-DD format",
          },
          endDate: {
            type: "string",
            description: "End date in YYYY-MM-DD format",
          },
          eventName: {
            type: "string",
            description: "Specific event name to filter by (optional)",
          },
        },
        required: ["startDate", "endDate"],
      },
    },
  • src/index.ts:130-260 (registration)
    Registration of all tools including getEvents in the ListToolsRequestHandler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "runReport",
            description: "Run a report to get analytics data",
            inputSchema: {
              type: "object",
              properties: {
                startDate: {
                  type: "string",
                  description: "Start date in YYYY-MM-DD format",
                },
                endDate: {
                  type: "string",
                  description: "End date in YYYY-MM-DD format",
                },
                dimensions: {
                  type: "array",
                  items: {
                    type: "object",
                    properties: {
                      name: { type: "string" },
                    },
                    required: ["name"],
                  },
                  description: "Dimensions to group by (e.g., page, country)",
                },
                metrics: {
                  type: "array",
                  items: {
                    type: "object",
                    properties: {
                      name: { type: "string" },
                    },
                    required: ["name"],
                  },
                  description: "Metrics to include in the report",
                },
                dimensionFilter: {
                  type: "object",
                  description: "Filter for dimensions",
                },
              },
              required: ["startDate", "endDate", "metrics", "dimensions"],
            },
          },
          {
            name: "getPageViews",
            description: "Get page view metrics for a specific date range",
            inputSchema: {
              type: "object",
              properties: {
                startDate: {
                  type: "string",
                  description: "Start date in YYYY-MM-DD format",
                },
                endDate: {
                  type: "string",
                  description: "End date in YYYY-MM-DD format",
                },
                dimensions: {
                  type: "array",
                  items: { type: "string" },
                  description: "Dimensions to group by (e.g., page, country)",
                },
              },
              required: ["startDate", "endDate"],
            },
          },
          {
            name: "getActiveUsers",
            description: "Get active users metrics for a specific date range",
            inputSchema: {
              type: "object",
              properties: {
                startDate: {
                  type: "string",
                  description: "Start date in YYYY-MM-DD format",
                },
                endDate: {
                  type: "string",
                  description: "End date in YYYY-MM-DD format",
                },
              },
              required: ["startDate", "endDate"],
            },
          },
          {
            name: "getEvents",
            description: "Get event metrics for a specific date range",
            inputSchema: {
              type: "object",
              properties: {
                startDate: {
                  type: "string",
                  description: "Start date in YYYY-MM-DD format",
                },
                endDate: {
                  type: "string",
                  description: "End date in YYYY-MM-DD format",
                },
                eventName: {
                  type: "string",
                  description: "Specific event name to filter by (optional)",
                },
              },
              required: ["startDate", "endDate"],
            },
          },
          {
            name: "getUserBehavior",
            description:
              "Get user behavior metrics like session duration and bounce rate",
            inputSchema: {
              type: "object",
              properties: {
                startDate: {
                  type: "string",
                  description: "Start date in YYYY-MM-DD format",
                },
                endDate: {
                  type: "string",
                  description: "End date in YYYY-MM-DD format",
                },
              },
              required: ["startDate", "endDate"],
            },
          },
        ],
      };
  • Shared helper function fetchAnalyticsData used by getEvents and other tools to run the GA report and return JSON response.
    async function fetchAnalyticsData(
      reportConfig: Partial<Omit<RunReportRequest, "property">> & {
        dateRanges: RunReportRequest["dateRanges"];
        dimensions?: RunReportRequest["dimensions"];
        metrics?: RunReportRequest["metrics"];
      },
    ) {
      try {
        const [response] = await analyticsDataClient.runReport({
          property: `properties/${propertyId}`,
          ...reportConfig,
        });
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      } catch (error) {
        // Handle Google Analytics API errors
        if (error instanceof Error) {
          throw new McpError(
            ErrorCode.InternalError,
            `Google Analytics API error: ${error.message}`,
          );
        }
        throw new McpError(ErrorCode.InternalError, "An unexpected error occurred");
      }
    }
  • Helper function validateDateRange used in getEvents handler to validate input dates.
    function validateDateRange(startDate: string, endDate: string): void {
      if (!validateDateFormat(startDate)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          `Invalid startDate format. Expected YYYY-MM-DD, got: ${startDate}`,
        );
      }
    
      if (!validateDateFormat(endDate)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          `Invalid endDate format. Expected YYYY-MM-DD, got: ${endDate}`,
        );
      }
    
      if (new Date(startDate) > new Date(endDate)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          "startDate cannot be after endDate",
        );
      }
    }
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. It states 'Get event metrics' but doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, rate limits, pagination, or what the output format looks like (e.g., aggregated metrics vs. raw events). This leaves significant gaps for an agent to understand how to use 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 front-loads the core action ('Get event metrics') and specifies the key constraint ('for a specific date range'). There is no wasted wording, making it highly concise and well-structured.

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 complexity of a metrics tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'event metrics' entail (e.g., counts, averages, trends), how results are returned, or any behavioral context. This leaves the agent with insufficient information to handle the tool robustly.

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?

Schema description coverage is 100%, so the schema fully documents the parameters (startDate, endDate, eventName) with their types, formats, and optionality. The description adds no additional meaning beyond implying date-range filtering, which is already covered in the schema. This meets 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 verb ('Get') and resource ('event metrics') with scope ('for a specific date range'), making the purpose understandable. It doesn't explicitly distinguish from siblings like 'getActiveUsers' or 'getPageViews', but the focus on 'event metrics' provides some implicit 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 like 'getActiveUsers', 'getPageViews', 'getUserBehavior', or 'runReport'. It mentions a date range but doesn't specify if this is the primary tool for event metrics or if other tools might overlap in functionality.

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/ruchernchong/mcp-server-google-analytics'

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