Eppo ACTION
List Metrics
Retrieve all metrics defined in Eppo, including their names, IDs, descriptions, and minimum detectable effects. Use this tool to discover available metrics or find metric IDs needed when creating an experiment with Create Experiment. Filter by
entityId to scope results to a specific entity type, or by name to find metrics by partial name match. Set includeExperiments to true to include associated experiments in the response (requires limit ≤ 10). Supports pagination via limit and offset. See the documentation- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Eppo account once, then configure and run List Metrics 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: "eppo-list-metrics",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
eppo: { authProvisionId: "apn_xxxxxxx" },
entityId: 10,
name: "Name",
},
})
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": "eppo-list-metrics",
"configured_props": {
"eppo": { "authProvisionId": "apn_xxxxxxx" },
"entityId": 10,
"name": "Name"
}
}'// 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": "eppo",
},
},
},
)
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: "eppo-list-metrics",
arguments: {
entityId: 10,
name: "Name",
},
})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 |
|---|---|---|
entityId Entity ID | integer | The numeric entity type ID this metric measures (e.g. user, session). Use List Metrics to find the entity_id from any existing metric — all metrics in the same workspace typically share the same entity ID. Optional |
name Name | string | Will return only metrics with a name that contains this value Optional |
includeExperiments Include Experiments | boolean | Will return all experiments associated with the metrics (requires limit to be 10 or less) Optional |
limit Limit | integer | Maximum number of items to return per page (max 250). Optional |
offset Offset | integer | Offset the number of items in response 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
- eppo-list-metrics
- Version
- 0.0.2
- App
- Eppo
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗