Skip to main content
Glama

Amplitude

by io.github.pipeworx-io
OverviewAdmin

Amp Get User Activity

amp_get_user_activity
Read-onlyIdempotent

Get recent event activity timeline for a specific user. Returns events with timestamps, properties, and interactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax events to return (default 100, max 1000)
offsetNoPagination offset (default 0)
_apiKeyYesAmplitude API key
_secretKeyYesAmplitude secret key
amplitude_idYesAmplitude internal user ID (from amp_user_search results)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoUser identification
eventsNoRecent events for user

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "events": {
+      "description": "Recent events for user",
+      "items": {
+        "properties": {
+          "device_id": {
+            "description": "Device identifier",
+            "type": "string"
+          },
+          "event_type": {
+            "description": "Event name",
+            "type": "string"
+          },
+          "properties": {
+            "description": "Event-specific properties",
+            "type": "object"
+          },
+          "session_id": {
+            "description": "Session identifier",
+            "type": "string"
+          },
+          "timestamp": {
+            "description": "Unix timestamp in milliseconds",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "user": {
+      "description": "User identification",
+      "properties": {
+        "amplitude_id": {
+          "description": "Amplitude user ID",
+          "type": "string"
+        },
+        "user_id": {
+          "description": "App user ID",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-amplitude-api-key",
+    "_secretKey": "your-amplitude-secret-key",
+    "amplitude_id": "5f8c1a2b9e4d5c6f7g8h9i0j"
+  },
+  {
+    "_apiKey": "your-amplitude-api-key",
+    "_secretKey": "your-amplitude-secret-key",
+    "amplitude_id": "5f8c1a2b9e4d5c6f7g8h9i0j",
+    "limit": 50,
+    "offset": 100
+  }
+]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive, so the description's addition of 'returns events with timestamps, properties, and interactions' adds some value by hinting at the output structure. However, it does not disclose pagination behavior, authentication requirements, or the fact that it uses an internal user ID from amp_user_search.

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 a single sentence that concisely conveys the tool's purpose and output. It is front-loaded with the action and subject. However, it could be slightly more structured, e.g., by explicitly listing the returned fields.

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?

Given the existence of an output schema (not shown but present) and full parameter documentation, the description is fairly complete. It explains the core functionality and what is returned, though it does not mention pagination or the need for an amplitude_id from a previous search.

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?

The input schema has 100% description coverage for all 5 parameters, including limit, offset, API keys, and amplitude_id. The description only adds 'for a specific user,' which is already implied by the amplitude_id parameter. Thus, the description adds minimal semantic value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves a recent event activity timeline for a specific user, with timestamps, properties, and interactions. This verb-resource combination is specific and distinguishes it from sibling tools like amp_get_events (which may be broader) or amp_get_active_users (focused on active users).

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, such as amp_get_events or amp_user_search. It does not mention prerequisites, limitations, or when to avoid using it. The agent must infer usage from the tool name and context.

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

All Amplitude toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources