Amplitude

Amp Get Active Users

amp_get_active_users

Read-onlyIdempotent

Get active user counts by granularity (daily, weekly, or monthly) for a date range. Returns totals and trend data.

Input Schema

TableJSON Schema

Name	Required	Description
`m`	No	Metric: "active" (DAU), "new", or "returning" (default "active")
`end`	Yes	End date (YYYYMMDD)
`start`	Yes	Start date (YYYYMMDD)
`_apiKey`	Yes	Amplitude API key
`_secretKey`	Yes	Amplitude secret key

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	Detailed user metrics by granularity
`series`	No	Active user counts by time period

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Detailed user metrics by granularity",
+      "type": "object"
+    },
+    "series": {
+      "description": "Active user counts by time period",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Date period (YYYYMMDD)",
+            "type": "string"
+          },
+          "value": {
+            "description": "Active user count",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-amplitude-api-key",
+    "_secretKey": "your-amplitude-secret-key",
+    "end": "20240131",
+    "start": "20240101"
+  },
+  {
+    "_apiKey": "your-amplitude-api-key",
+    "_secretKey": "your-amplitude-secret-key",
+    "end": "20240131",
+    "m": "new",
+    "start": "20240101"
+  }
+]

First observedApr 22, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the bar is lower. The description adds that it 'Returns totals and trend data,' which is useful but does not disclose additional behavioral traits such as rate limits or data freshness.

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 sentences front-loaded with the verb and resource. Concise with no wasted words. However, the granularity phrasing could be more precise to avoid confusion.

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 presence of a rich annotation set and an output schema, the description covers the tool's purpose and key features (totals, trend data, granularity). It is adequate for a simple data retrieval tool, though minor inaccuracies around granularity exist.

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 baseline is 3. The description mentions 'granularity (daily, weekly, or monthly),' which is not reflected in the schema (the 'm' parameter is for metric, not granularity). This adds context but potentially introduces inconsistency.

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 identifies the verb 'Get', resource 'active user counts', and specifies the returned data (totals and trend data). It distinguishes from sibling tools like amp_get_events or amp_get_retention by focusing on active user counts.

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 description mentions granularity options (daily, weekly, monthly) and date range, which implies usage context, but lacks explicit guidance on when to use this tool versus alternatives like amp_get_events. No when-not or exclusion criteria are stated.

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

All Amplitude tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.