Skip to main content
Glama

Amp User Search

amp_user_search
Read-onlyIdempotent

Search for users by ID or property (e.g., email, user_id). Returns matching profiles with properties, event history, and segments.

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": {
      "user": "user123@example.com",
      "_apiKey": "your-amplitude-api-key",
      "_secretKey": "your-amplitude-secret-key"
    },
    "name": "amp_user_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUser search term (email, user_id, or Amplitude ID)
regionNoData region: "us" (default) or "eu" for EU-residency projects
_apiKeyYesAmplitude API key
_secretKeyYesAmplitude secret key

Output Schema

NameRequiredDescriptionDefault
matchesNoMatching user profiles

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": {
      +    "matches": {
      +      "description": "Matching user profiles",
      +      "items": {
      +        "properties": {
      +          "amplitude_id": {
      +            "description": "Amplitude internal user ID",
      +            "type": "string"
      +          },
      +          "email": {
      +            "description": "User email address",
      +            "type": "string"
      +          },
      +          "last_used": {
      +            "description": "Last activity timestamp",
      +            "type": "string"
      +          },
      +          "properties": {
      +            "description": "User custom properties",
      +            "type": "object"
      +          },
      +          "segments": {
      +            "description": "User segment memberships",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "user_id": {
      +            "description": "User's ID from app",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "_apiKey": "your-amplitude-api-key",
      +    "_secretKey": "your-amplitude-secret-key",
      +    "user": "user123@example.com"
      +  }
      +]
  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, openWorld and non-destructive, so the safety profile is covered. The description adds value by listing what the response contains, but it does not disclose important behavior for a search tool: exact vs. substring matching, behavior when multiple or zero users match, or rate-limit/API-key requirements.

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 tight, front-loaded sentences with no filler; purpose comes first and return contents second. Minor redundancy exists because the email/user_id examples duplicate the schema's parameter description.

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?

With rich annotations, a full output schema, and 100% parameter coverage, the description only needs to establish purpose and result scope, which it does. The remaining gap is match semantics and pagination/result-set size, which an agent would still need to infer.

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 all four parameters including the region default and credential fields are already documented. The description's parenthetical ("e.g., email, user_id") largely restates the schema's own description for the user field, adding no new semantics.

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 ("Search for users") and states the return contents (profiles with properties, event history, segments). It is clearly distinct from siblings like amp_get_user_activity or amp_get_events by resource, though it never names an alternative explicitly.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives (e.g., amp_get_user_activity for activity-only queries). The only usage signal is the implicit 'look up a user' framing embedded in the parameter examples, which is not real routing guidance.

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.