Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_apiKey": "your-amplitude-api-key",
      "_secretKey": "your-amplitude-secret-key",
      "amplitude_id": "5f8c1a2b9e4d5c6f7g8h9i0j"
    },
    "name": "amp_get_user_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax events to return (default 100, max 1000)
offsetNoPagination offset (default 0)
regionNoData region: "us" (default) or "eu" for EU-residency projects
_apiKeyYesAmplitude API key
_secretKeyYesAmplitude secret key
amplitude_idYesAmplitude internal user ID (from amp_user_search results)

Output Schema

NameRequiredDescriptionDefault
userNoUser identification
eventsNoRecent events for user

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / region
      Added value: +{
      +  "description": "Data region: \"us\" (default) or \"eu\" for EU-residency projects",
      +  "type": "string"
      +}
  2. 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"
      +}
  3. 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
      +  }
      +]
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds that results are a timeline carrying timestamps, properties, and interactions, but says nothing about how far back 'recent' extends, what pagination does, or any rate limits or size caps on the response.

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 short sentences, front-loaded with the verb and scope, with no filler or hedging. The second sentence partly duplicates what the output schema already conveys about returned fields, which is the only slack.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, and all six parameters are documented in-schema. What is missing is definition-level context an agent needs to call it well: the meaning of 'recent', how paging should be driven, and any data-freshness caveat. Adequate but with clear gaps.

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 limit, offset, region and the credential/id parameters are already documented, including defaults and the 1000 max. The description adds no parameter meaning beyond that, so the baseline of 3 applies; 'specific user' only restates the amplitude_id requirement.

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 concrete verb+resource pair: 'Get recent event activity timeline for a specific user.' An agent can tell this returns per-user event history rather than events, retention, or active-user metrics. It does not explicitly contrast itself with the sibling amp_get_events, which likely overlaps.

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?

There is no when-to-use or when-not-to-use guidance and no mention of what makes this the right choice over amp_get_events or amp_get_active_users. The only implicit signal is 'for a specific user', which requires the amplitude_id parameter and is already visible in the schema.

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.