Skip to main content
Glama
mendeel

Mixpanel MCP

by mendeel

query_segmentation_report

Analyze event patterns by segmenting user behavior based on properties to compare how different groups interact with your product.

Instructions

Segment events by properties. Useful for analyzing how different user segments behave and comparing event patterns across groups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoThe Mixpanel project ID. Optional since it has a default.
eventYesThe event to segment
from_dateYesThe date in yyyy-mm-dd format to begin querying from (inclusive)
to_dateYesThe date in yyyy-mm-dd format to query to (inclusive)
onYesThe property to segment by
whereNoJSON string representing additional filters
unitNoThe time unit for segmentation, defaults to day

Implementation Reference

  • The handler function that implements the core logic of the query_segmentation_report tool by making an authenticated GET request to Mixpanel's /segmentation API endpoint with the specified event, date range, segmentation property, and filters.
    async function handleQuerySegmentationReport(args: any, config: any) {
      const { 
        project_id = config.DEFAULT_PROJECT_ID, 
        event, 
        from_date, 
        to_date, 
        on, 
        where, 
        unit = "day" 
      } = args;
      
      try {
        const credentials = `${config.SERVICE_ACCOUNT_USER_NAME}:${config.SERVICE_ACCOUNT_PASSWORD}`;
        const encodedCredentials = Buffer.from(credentials).toString('base64');
        
        let url = `${config.MIXPANEL_BASE_URL}/segmentation?project_id=${project_id}&event=${encodeURIComponent(event)}&from_date=${from_date}&to_date=${to_date}&on=${encodeURIComponent(on)}&unit=${unit}`;
        
        if (where) {
          url += `&where=${encodeURIComponent(where)}`;
        }
        
        const options = {
          method: 'GET',
          headers: {
            'accept': 'application/json',
            'authorization': `Basic ${encodedCredentials}`
          }
        };
        
        const response = await fetch(url, options);
        
        if (!response.ok) {
          const errorText = await response.text();
          throw new Error(`HTTP error! status: ${response.status} - ${errorText}`);
        }
        
        const data = await response.json();
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(data)
            }
          ]
        };
      } catch (error: unknown) {
        console.error("Error querying segmentation report:", error);
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [
            {
              type: "text",
              text: `Error querying segmentation report: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
    }
  • JSON schema defining the input parameters for the query_segmentation_report tool, including required fields event, from_date, to_date, on, and optional project_id, where, unit.
    inputSchema: {
      type: "object",
      properties: {
        project_id: {
          type: "string",
          description: "The Mixpanel project ID. Optional since it has a default."
        },
        event: {
          type: "string",
          description: "The event to segment"
        },
        from_date: {
          type: "string",
          description: "The date in yyyy-mm-dd format to begin querying from (inclusive)"
        },
        to_date: {
          type: "string",
          description: "The date in yyyy-mm-dd format to query to (inclusive)"
        },
        on: {
          type: "string",
          description: "The property to segment by"
        },
        where: {
          type: "string",
          description: "JSON string representing additional filters"
        },
        unit: {
          type: "string",
          enum: ["hour", "day", "week", "month"],
          description: "The time unit for segmentation, defaults to day"
        }
      },
      required: ["event", "from_date", "to_date", "on"]
    }
  • src/index.ts:642-643 (registration)
    Dispatch case in the CallToolRequestSchema handler that registers and routes calls to the specific handleQuerySegmentationReport function.
    case "query_segmentation_report":
      return await handleQuerySegmentationReport(args, { SERVICE_ACCOUNT_USER_NAME, SERVICE_ACCOUNT_PASSWORD, DEFAULT_PROJECT_ID, MIXPANEL_BASE_URL });
  • src/index.ts:531-569 (registration)
    Tool definition registered in the ListToolsRequestSchema response, including name, description, and input schema.
    {
      name: "query_segmentation_report",
      description: "Segment events by properties. Useful for analyzing how different user segments behave and comparing event patterns across groups.",
      inputSchema: {
        type: "object",
        properties: {
          project_id: {
            type: "string",
            description: "The Mixpanel project ID. Optional since it has a default."
          },
          event: {
            type: "string",
            description: "The event to segment"
          },
          from_date: {
            type: "string",
            description: "The date in yyyy-mm-dd format to begin querying from (inclusive)"
          },
          to_date: {
            type: "string",
            description: "The date in yyyy-mm-dd format to query to (inclusive)"
          },
          on: {
            type: "string",
            description: "The property to segment by"
          },
          where: {
            type: "string",
            description: "JSON string representing additional filters"
          },
          unit: {
            type: "string",
            enum: ["hour", "day", "week", "month"],
            description: "The time unit for segmentation, defaults to day"
          }
        },
        required: ["event", "from_date", "to_date", "on"]
      }
    },
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 describes the analytical purpose but doesn't mention any behavioral traits: no information about whether this is a read-only operation, potential rate limits, authentication requirements, data freshness, or what the output format looks like. For a query tool with 7 parameters, this leaves significant gaps in understanding how the tool behaves.

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

Conciseness4/5

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

The description is appropriately concise with two sentences that directly address the tool's purpose and utility. The first sentence states the core functionality, and the second explains its analytical value. There's no wasted verbiage, though it could be slightly more structured by front-loading more specific information about what makes this segmentation unique.

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?

For a 7-parameter query tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address what the tool returns (no output schema exists), doesn't mention any constraints or limitations, and provides minimal behavioral context. Given the complexity of segmentation analysis and the rich parameter set, users need more guidance about what to expect from this operation.

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 already documents all 7 parameters thoroughly. The description adds no specific parameter information beyond what's in the schema - it doesn't explain how parameters interact, provide examples of valid 'where' JSON strings, or clarify the relationship between 'event' and 'on' parameters. The baseline of 3 is appropriate when the schema does the heavy lifting.

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: 'Segment events by properties' with the goal of 'analyzing how different user segments behave and comparing event patterns across groups.' This specifies both the action (segment) and resource (events by properties), though it doesn't explicitly differentiate from sibling tools like query_funnel_report or query_retention_report.

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. It mentions the tool is 'useful for analyzing how different user segments behave,' but doesn't specify when to choose it over sibling tools like query_funnel_report, query_insights_report, or aggregated_event_property_values. No exclusions or prerequisites are mentioned.

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/mendeel/mixpanel-mcp'

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