Skip to main content
Glama
ruchernchong

mcp-server-google-analytics

by ruchernchong

getPageViews

Retrieve page view metrics from Google Analytics 4 for specified date ranges and dimensions to analyze website traffic patterns.

Instructions

Get page view 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
dimensionsNoDimensions to group by (e.g., page, country)

Implementation Reference

  • Handler for the getPageViews tool. Extracts startDate, endDate, and optional dimensions (defaults to 'page'), validates the date range, and invokes fetchAnalyticsData with appropriate dimensions and the 'screenPageViews' metric.
    case "getPageViews": {
      const {
        startDate,
        endDate,
        dimensions = ["page"],
      } = args as {
        startDate: string;
        endDate: string;
        dimensions?: string[];
      };
    
      validateDateRange(startDate, endDate);
    
      return fetchAnalyticsData({
        dateRanges: [{ startDate, endDate }],
        dimensions: dimensions.map((dimension) => ({ name: dimension })),
        metrics: [{ name: "screenPageViews" }],
      });
    }
  • src/index.ts:177-199 (registration)
    Registration of the getPageViews tool in the ListTools response, including name, description, and input schema.
    {
      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"],
      },
    },
  • Helper function fetchAnalyticsData that performs the actual Google Analytics API call using runReport and formats the 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 by the 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 of behavioral disclosure. It states the tool 'Get[s] page view metrics,' implying a read-only operation, but doesn't cover aspects like authentication needs, rate limits, error handling, or what the metrics include (e.g., counts, trends). This is a significant gap for a tool with no annotation coverage.

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 purpose without unnecessary details. It avoids redundancy and wastes no words, making it highly concise and well-structured for quick understanding.

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

Completeness3/5

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

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavioral traits, usage context, and output format, which are needed for full completeness. Without annotations or output schema, more guidance would be beneficial.

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%, with clear descriptions for all parameters (e.g., date formats, dimensions grouping). The description adds no additional parameter semantics beyond implying date-range filtering, which is already covered in the schema. This meets the baseline score of 3 when the schema handles most documentation.

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 tool's purpose as retrieving 'page view metrics for a specific date range,' which includes a specific verb ('Get') and resource ('page view metrics'). However, it doesn't distinguish this from sibling tools like 'getActiveUsers' or 'getEvents,' which likely retrieve different types of metrics, so it doesn't achieve full 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' or 'runReport.' It mentions a 'specific date range' but doesn't specify prerequisites, exclusions, or comparative contexts, leaving the agent to infer usage based on tool names alone.

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