Skip to main content
Glama
ruchernchong

mcp-server-google-analytics

by ruchernchong

runReport

Retrieve Google Analytics 4 data by specifying date ranges, dimensions, and metrics to generate custom reports for analysis.

Instructions

Run a report to get analytics data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateYesStart date in YYYY-MM-DD format
endDateYesEnd date in YYYY-MM-DD format
dimensionsYesDimensions to group by (e.g., page, country)
metricsYesMetrics to include in the report
dimensionFilterNoFilter for dimensions

Implementation Reference

  • Handler for the 'runReport' tool: destructures arguments, validates date range, and calls the shared fetchAnalyticsData helper with the report configuration.
    case "runReport": {
      const {
        startDate,
        endDate,
        dimensions = [],
        metrics = [],
        dimensionFilter,
      } = args as {
        startDate: string;
        endDate: string;
        dimensions?: { name: string }[];
        metrics?: { name: string }[];
        dimensionFilter?: object;
      };
    
      validateDateRange(startDate, endDate);
    
      return fetchAnalyticsData({
        dateRanges: [{ startDate, endDate }],
        dimensions,
        metrics,
        ...(dimensionFilter && { dimensionFilter }),
      });
    }
  • Input schema definition for the 'runReport' tool, specifying required date ranges, dimensions, metrics, and optional filters.
      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"],
    },
  • src/index.ts:134-176 (registration)
    Tool registration object for 'runReport' returned in ListTools response, including name, description, and full input schema.
      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"],
      },
    },
  • Shared helper function that performs the actual Google Analytics Data API runReport call and formats the response as MCP content.
    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");
      }
    }
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 mentions 'run a report' which implies a read operation, but fails to disclose critical traits like whether it's safe (non-destructive), requires authentication, has rate limits, or what the output format looks like. This is a significant gap for a tool with multiple parameters.

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 with zero waste: 'Run a report to get analytics data'. 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 tool's complexity (5 parameters, nested objects, no output schema) and lack of annotations, the description is incomplete. It doesn't explain what the report returns, how results are structured, or behavioral aspects like safety and performance, leaving the agent with insufficient context for 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 all 5 parameters (e.g., startDate, endDate, dimensions, metrics, dimensionFilter) with descriptions. The tool description adds no additional meaning beyond what the schema provides, resulting in a baseline score of 3.

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

Purpose3/5

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

The description 'Run a report to get analytics data' states a vague purpose with the verb 'run' and resource 'report', but it lacks specificity about what kind of analytics or how it differs from sibling tools like getActiveUsers or getEvents. It doesn't clearly distinguish itself from alternatives, making it only adequate.

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 the sibling tools (getActiveUsers, getEvents, etc.). There's no mention of context, prerequisites, or alternatives, leaving the agent without clear usage instructions.

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