Mixpanel (Service Account) ACTION
List Events
List the names of the events tracked in this Mixpanel project over the last 31 days, ordered by how often they were fired. Start here when you do not already know the exact event name a question refers to - most other tools need an exact, case-sensitive name. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Mixpanel (Service Account) account once, then configure and run List Events from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "mixpanel_service_account-list-events",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
mixpanel_service_account: { authProvisionId: "apn_xxxxxxx" },
analysisType: "Analysis Type",
limit: 10,
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "mixpanel_service_account-list-events",
"configured_props": {
"mixpanel_service_account": { "authProvisionId": "apn_xxxxxxx" },
"analysisType": "Analysis Type",
"limit": 10
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "mixpanel_service_account",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "mixpanel_service_account-list-events",
arguments: {
analysisType: "Analysis Type",
limit: 10,
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
analysisType Analysis Type | string | How events are counted when ranking them. Required |
limit Limit | integer | The maximum number of event names to return. Defaults to 255. Optional |
workspaceId Workspace ID | integer | The ID of the Data View to query. Only needed for projects that use Data Views; leave it empty otherwise. It is the segment after /view/ in a project URL such as https://mixpanel.com/project/1234/view/5678/app/boards. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- mixpanel_service_account-list-events
- Version
- 0.0.1
- App
- Mixpanel (Service Account)
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗