Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mixpanel_get_events

Read-onlyIdempotent

Retrieve Mixpanel event analytics for a date range, with optional event filters and aggregation by time unit.

Instructions

Get Mixpanel event analytics data for a date range.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service_account_username": "<service_account_username>",
      "service_account_secret": "<service_account_secret>",
      "project_id": "<project_id>"
    },
    "name": "mixpanel_get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoAggregation type (default: general)
unitNoTime unit (default: day)
eventNoEvent names to filter by
to_dateNoEnd date (YYYY-MM-DD, default: today)
from_dateNoStart date (YYYY-MM-DD, default: 7 days ago)
project_idYesMixpanel project ID
service_account_secretYesMixpanel Service Account secret
service_account_usernameYesMixpanel Service Account username

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.9
  2. Removed
  3. Addedv0.1.5

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only the date-range scoping, and says nothing about authentication expectations for the required service-account credentials or about response shape/size.

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?

A single front-loaded sentence with no filler. It is efficient, though it is arguably too sparse for a tool with eight parameters rather than being trimmed of waste.

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 an eight-parameter analytics query with three required auth parameters and no output schema, the description leaves the agent without any sense of what the returned data looks like or how the aggregation/time-unit choices affect it. Annotations and schema cover safety and parameters, but the result semantics gap remains.

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 both enums (type, unit) and defaults documented in the schema. The description adds no meaning beyond 'date range' — it does not explain what the aggregation types produce or how multi-event filtering behaves, so it neither helps nor harms.

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 ('Get Mixpanel event analytics data') plus a scope qualifier ('for a date range'). It is clearly distinct from mixpanel_get_funnels and mixpanel_get_retention in substance, but it never names those siblings to make the distinction explicit.

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?

No guidance on when to use this rather than mixpanel_get_funnels, mixpanel_get_retention, or mixpanel_export_data. The date range is the only implied selection condition, and there are no prerequisites or exclusions stated.

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

Deploy Server

Other Tools