Skip to main content
Glama

Track event

track_event
Destructive

Record something a customer did (e.g. signed_up, cart_abandoned, trial_ending), by user_id and/or phone. It starts or advances any active automation listening for that event. external_id (their Mixpanel distinct_id, when not user_id) puts the texts it starts on their Mixpanel profile.

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": {
      "event": "<event>"
    },
    "name": "track_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventYesLetters, digits, and _ . : -
phoneNoThe person's number in E.164
user_idNoYour id for the person. Sent with phone, it links the two, so later events need only user_id
propertiesNoUp to 20 scalar values; usable as merge fields and in conditions.
external_idNoOptional. The person's id in your analytics tool (their Mixpanel distinct_id; `mixpanel_distinct_id` is accepted too), when it is not user_id. Kept on the event as mixpanel_distinct_id; texts the event starts land on that profile in Mixpanel. Without it, user_id is used.
idempotency_keyNoOptional. A unique key for this call: a retry with the same key is recorded once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / external_id
      Added value: +{
      +  "description": "Optional. The person's id in your analytics tool (their Mixpanel distinct_id; `mixpanel_distinct_id` is accepted too), when it is not user_id. Kept on the event as mixpanel_distinct_id; texts the event starts land on that profile in Mixpanel. Without it, user_id is used.",
      +  "maxLength": 255,
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / phone / description
      Added value: +"The person's number in E.164"
    • addedInput schema / properties / user_id / description
      Added value: +"Your id for the person. Sent with phone, it links the two, so later events need only user_id"
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, idempotentHint=false, openWorldHint=true, but say nothing about what actually happens. The description supplies the critical consequence the agent needs: the event 'starts or advances any active automation listening for that event', plus where started texts land in Mixpanel. It omits that idempotency_key exists as a retry safeguard, which is the one notable gap.

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?

Three tight sentences, front-loaded with the action and examples before the automation side effect. Dense but no filler; only the external_id sentence leans slightly on schema-provided detail.

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?

For a mutation tool with no output schema and a nested properties object, the definition covers the essential behavior: identity requirements, automation triggering, and Mixpanel attribution. Minor omissions (idempotency, merge-field usage of properties) are largely covered by the schema itself.

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% and the schema descriptions are already detailed, especially for external_id and user_id linking, so the baseline is 3. The description adds only a modest clarification ('by user_id and/or phone' needing at least one identifier) and otherwise restates Mixpanel behavior already documented in the schema.

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 ('Record something a customer did') with concrete example event names (signed_up, cart_abandoned, trial_ending) and the resulting side effect. It does not explicitly distinguish itself from nearby siblings like record_conversion or replay_event, but the scope is unambiguous.

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?

Implies usage via 'by user_id and/or phone', which conveys that identity must be supplied, and notes external_id is used 'when not user_id'. There is no explicit when-to-use/when-not guidance against alternatives such as record_conversion or send_message, so the agent must infer the boundary.

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.