Skip to main content
Glama

Mixpanel Get Events

mixpanel_get_events
Read-onlyIdempotent

Query event data from Mixpanel for a date range. Returns event counts and properties. Example: get_events({ from_date: "2024-01-01", to_date: "2024-01-31", event: "Sign Up", _apiKey: "your_api_secret" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event": "Sign Up",
      "_apiKey": "your-mixpanel-api-key",
      "to_date": "2024-01-31",
      "from_date": "2024-01-01"
    },
    "name": "mixpanel_get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventNoOptional specific event name to filter by, e.g. "Sign Up", "Purchase"
_apiKeyYesMixpanel API secret (used for Basic auth)
to_dateYesEnd date in YYYY-MM-DD format, e.g. "2024-01-31"
from_dateYesStart date in YYYY-MM-DD format, e.g. "2024-01-01"

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds only that the result contains event counts and properties; it says nothing about volume limits, pagination, wide date-range behavior, or failure modes for an open-world remote query.

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?

Two compact sentences with the purpose and return shape front-loaded, followed by a short example. The example largely duplicates the schema's own examples and embeds a placeholder API secret, which is minor redundancy but not harmful.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and all four parameters are fully documented in the schema. What remains thin is operational context for an open-world query — result caps and large-range behavior — but nothing essential for correct invocation is missing.

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 coverage is 100% with per-field descriptions including date format and the optional event filter, so the schema carries the load. The description's example call repeats those same fields without adding format, default, or constraint details beyond what the schema states.

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?

States a specific verb and resource ("Query event data from Mixpanel") scoped to a date range, and adds that it returns event counts and properties. It does not explicitly distinguish itself from siblings like get_funnels or get_retention, so an agent must infer that this is raw event data rather than funnel/retention analysis.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The date-range example implies a typical usage pattern, but there is no explicit when-to-use or when-not-to-use guidance and no reference to the sibling tools that cover funnels and retention. The agent must infer the boundary from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.