Regtransfers/amplitude-automation

@ Amplitude Automation via Rube MCP

Automate Amplitude product analytics through Composio's Amplitude toolkit via Rube MCP.

@ Prerequisites

• Rube MCP must be connected (RUBESEARCHTOOLS available)
• Active Amplitude connection via RUBEMANAGECONNECTIONS with toolkit amplitude
• Always call RUBESEARCHTOOLS first to get current tool schemas

@ Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
2. Call RUBEMANAGECONNECTIONS with toolkit amplitude
3. If connection is not ACTIVE, follow the returned auth link to complete Amplitude authentication
4. Confirm connection status shows ACTIVE before running any workflows

@ Core Workflows

@ 1. Send Events

When to use: User wants to track events or send event data to Amplitude

Tool sequence:

1. AMPLITUDESENDEVENTS - Send one or more events to Amplitude [Required]

Key parameters:

• events: Array of event objects, each containing:
• eventtype: Name of the event (e.g., 'pageview', 'purchase')
• userid: Unique user identifier (required if no deviceid)
• deviceid: Device identifier (required if no userid)
• event_properties: Object with custom event properties
• user_properties: Object with user properties to set
• time: Event timestamp in milliseconds since epoch

Pitfalls:

• At least one of userid or deviceid is required per event
• event_type is required for every event; cannot be empty
• time must be in milliseconds (13-digit epoch), not seconds
• Batch limit applies; check schema for maximum events per request
• Events are processed asynchronously; successful API response does not mean data is immediately queryable

@ 2. Get User Activity

When to use: User wants to view event history for a specific user

Tool sequence:

1. AMPLITUDEFINDUSER - Find user by ID or property [Prerequisite]
2. AMPLITUDEGETUSER_ACTIVITY - Retrieve user's event stream [Required]

Key parameters:

• user: Amplitude internal user ID (from FIND_USER)
• offset: Pagination offset for event list
• limit: Maximum number of events to return

Pitfalls:

• user parameter requires Amplitude's internal user ID, NOT your application's user_id
• Must call FINDUSER first to resolve your userid to Amplitude's internal ID
• Activity is returned in reverse chronological order by default
• Large activity histories require pagination via offset

@ 3. Find and Identify Users

When to use: User wants to look up users or set user properties

Tool sequence:

1. AMPLITUDEFINDUSER - Search for a user by various identifiers [Required]
2. AMPLITUDE_IDENTIFY - Set or update user properties [Optional]

Key parameters:

• For FIND_USER:
• user: Search term (user_id, email, or Amplitude ID)
• For IDENTIFY:
• user_id: Your application's user identifier
• deviceid: Device identifier (alternative to userid)
• user_properties: Object with $set, $unset, $add, $append operations

Pitfalls:

• FINDUSER searches across userid, device_id, and Amplitude ID
• IDENTIFY uses special property operations ($set, $unset, $add, $append)
• $set overwrites existing values; $setOnce only sets if not already set
• At least one of userid or deviceid is required for IDENTIFY
• User property changes are eventually consistent; not immediate

@ 4. Manage Cohorts

When to use: User wants to list cohorts, view cohort details, or update cohort membership

Tool sequence:

1. AMPLITUDELISTCOHORTS - List all saved cohorts [Required]
2. AMPLITUDEGETCOHORT - Get detailed cohort information [Optional]
3. AMPLITUDEUPDATECOHORT_MEMBERSHIP - Add/remove users from a cohort [Optional]
4. AMPLITUDECHECKCOHORT_STATUS - Check async cohort operation status [Optional]

Key parameters:

• For LIST_COHORTS: No required parameters
• For GETCOHORT: cohortid (from list results)
• For UPDATECOHORTMEMBERSHIP:
• cohort_id: Target cohort ID
• memberships: Object with add and/or remove arrays of user IDs
• For CHECKCOHORTSTATUS: request_id from update response

Pitfalls:

• Cohort IDs are required for all cohort-specific operations
• UPDATECOHORTMEMBERSHIP is asynchronous; use CHECKCOHORTSTATUS to verify
• request_id from the update response is needed for status checking
• Maximum membership changes per request may be limited; chunk large updates
• Only behavioral cohorts support API membership updates

@ 5. Browse Event Categories

When to use: User wants to discover available event types and categories in Amplitude

Tool sequence:

1. AMPLITUDEGETEVENT_CATEGORIES - List all event categories [Required]

Key parameters:

• No required parameters; returns all configured event categories

Pitfalls:

• Categories are configured in Amplitude UI; API provides read access
• Event names within categories are case-sensitive
• Use these categories to validate event_type values before sending events

@ Common Patterns

@ ID Resolution

Application user_id -> Amplitude internal ID:

1. Call AMPLITUDE_FIND_USER with user=your_user_id
2. Extract Amplitude's internal user ID from response
3. Use internal ID for GET_USER_ACTIVITY

Cohort name -> Cohort ID:

1. Call AMPLITUDE_LIST_COHORTS
2. Find cohort by name in results
3. Extract id for cohort operations

@ User Property Operations

Amplitude IDENTIFY supports these property operations:

• $set: Set property value (overwrites existing)
• $setOnce: Set only if property not already set
• $add: Increment numeric property
• $append: Append to list property
• $unset: Remove property entirely

Example structure:

{
  "user_properties": {
    "$set": {"plan": "premium", "company": "Acme"},
    "$add": {"login_count": 1}
  }
}

@ Async Operation Pattern

For cohort membership updates:

1. Call AMPLITUDE_UPDATE_COHORT_MEMBERSHIP -> get request_id
2. Call AMPLITUDE_CHECK_COHORT_STATUS with request_id
3. Repeat step 2 until status is 'complete' or 'error'

@ Known Pitfalls

User IDs:

• Amplitude has its own internal user IDs separate from your application's
• FIND_USER resolves your IDs to Amplitude's internal IDs
• GETUSERACTIVITY requires Amplitude's internal ID, not your user_id

Event Timestamps:

• Must be in milliseconds since epoch (13 digits)
• Seconds (10 digits) will be interpreted as very old dates
• Omitting timestamp uses server receive time

Rate Limits:

• Event ingestion has throughput limits per project
• Batch events where possible to reduce API calls
• Cohort membership updates have async processing limits

Response Parsing:

• Response data may be nested under data key
• User activity returns events in reverse chronological order
• Cohort lists may include archived cohorts; check status field
• Parse defensively with fallbacks for optional fields

@ Quick Reference

Task; Tool Slug; Key Params

Send events; AMPLITUDESENDEVENTS; events (array) Find user; AMPLITUDEFINDUSER; user Get user activity; AMPLITUDEGETUSER_ACTIVITY; user, offset, limit Identify user; AMPLITUDEIDENTIFY; userid, user_properties List cohorts; AMPLITUDELISTCOHORTS; (none) Get cohort; AMPLITUDEGETCOHORT; cohort_id Update cohort members; AMPLITUDEUPDATECOHORTMEMBERSHIP; cohortid, memberships Check cohort status; AMPLITUDECHECKCOHORTSTATUS; requestid List event categories; AMPLITUDEGETEVENT_CATEGORIES; (none)

@ When to Use This skill is applicable to execute the workflow or actions described in the overview.

@ Limitations

• Use this skill only when the task clearly matches the scope described above.
• never treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.