Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mixpanel_get_retention

Read-onlyIdempotent

Retrieve Mixpanel user retention analytics by event, date range, and time unit to measure how many users return after acquisition.

Instructions

Get user retention analytics from Mixpanel.

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_retention"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoTime unit (default: day)
eventNoRetention event to measure
to_dateNoEnd date (YYYY-MM-DD)
from_dateNoStart date (YYYY-MM-DD, default: 30 days ago)
born_eventNoEvent that defines user acquisition
project_idYesMixpanel project ID
retention_typeNoRetention type (default: birth)
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

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds nothing beyond that: it does not explain the difference between 'birth' and 'compactness' retention, the 30-day default window, or any rate limits or auth behavior — notable gaps for a read-only analytics query.

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

Conciseness3/5

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

It is one short sentence with no filler, but it is under-specified rather than efficiently concise: for a 9-parameter analytics tool, the single clause leaves the important semantics unstated.

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?

Nine parameters including three required credentials, two enums and a date range, with no output schema, mean the description should carry more weight. It does not explain what a retention result looks like or how the cohort and unit options shape it.

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 every parameter already carries documentation and the baseline is 3. The description adds no extra meaning, such as how born_event and event interact or how retention_type changes the results, so it does not exceed the baseline.

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 names a specific verb and resource ('Get user retention analytics') from a named provider, which is enough to separate it from siblings like mixpanel_get_events and mixpanel_get_funnels. It does not explicitly say what makes retention distinct from those, so it falls short of a 5.

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 gives no guidance on when to choose retention over funnels or events, no prerequisites, and no note that service-account credentials are required. The agent must infer the use case 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.

Deploy Server

Other Tools