Connect Your AI Agent with Eppo for Slack

Create or update a metric in Eppo. Omit metricId to create a new metric; provide metricId to update an existing one. Use this when the user wants to define a new KPI/metric or update the definition of an existing metric. Use List Metrics to find the numeric metricId for an update and to look up the entityId from existing metrics. entityId is required — find it in the entity_id field of any existing metric returned by List Metrics. The minimumDetectableEffect is a decimal representing the smallest meaningful relative change (e.g. 0.05 for 5%). Provide exactly one metric definition: numerator (standard or ratio metrics), percentile, or funnelAggregation. For ratio metrics, also provide denominator. Set denominator to the JSON literal null for non-ratio metrics. IMPORTANT: metric_event_measure_id is a data-source ID from your Eppo data pipeline configuration — obtain it from your Eppo workspace's data integration settings. It is NOT the same as a metric ID or aggregation ID. The Eppo API requires the full numerator/percentile/funnel definition even for metadata-only updates. See the documentation - Create Metric and See the documentation - Update Metric

Enable or disable a feature flag in a specific environment in Eppo. Use this when the user wants to turn a flag on or off in Production, Test, or another environment. Use List Feature Flags or Get Feature Flag first to find the numeric flagId and to discover valid environmentId values from the flag's environments array. See the documentation

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

Retrieve all feature flags in Eppo with their name, key, enabled status, and allocation configuration. Use this tool when a user wants to see all flags, find a specific flag by name, or discover flag IDs needed by Get Feature Flag or Toggle Feature Flag. Set includeArchived to also return archived flags. See the documentation

Retrieve all experiments in Eppo with their name, key, status, entity ID, and assignment source ID. Use this to discover experiment IDs for Get Experiment Results, or find entity_id values needed to create new experiments. Filter by type (all, experiments, or holdouts), experimentKey, entityId, tagNames, isDeleted, updatedSince, or createdSince to narrow results. Set withCalculatedMetrics or withFullCupedData to include additional metric data in the response. See the documentation

Retrieve full details for a single feature flag including its allocation rules, assignment configuration, and variations. Use this tool when the user asks about a specific flag's configuration or assignment logic. Use List Feature Flags first to find the numeric flagId — Eppo uses integer IDs, not string keys, for flag lookups. See the documentation

Retrieve full details and analysis results for a single experiment, including outcome, winning variant key, key takeaways, and per-metric results. Use this when the user asks about experiment performance, results, or analysis for a specific experiment. Use List Experiments first to find the numeric experimentId — Eppo uses integer IDs for experiment lookups. Set allowDeleted to true to include soft-deleted experiments in the response. See the documentation

Create a new feature flag in Eppo with a unique key, display name, entity ID, variations, and optional tags. Use this when the user wants to add a new feature flag. The key must be a unique URL-safe slug (e.g. my-new-feature). Duplicate keys are rejected by the API. IMPORTANT: Each variation requires variant_key (unique slug) and type (must be STRING, INTEGER, or JSON — uppercase). Do NOT use key or value fields. Example: [{"variant_key": "on", "type": "STRING", "name": "On"}, {"variant_key": "off", "type": "STRING", "name": "Off"}]. Use List Feature Flags to verify the flag was created. See the documentation

Create a new experiment analysis in Eppo. Use List Experiments first to find valid entityId and assignmentSourceId values — these numeric IDs are not available separately and must be copied from an existing experiment. Use List Metrics to find metric IDs to attach to the experiment. experimentKey must be a unique slug matching the assignment logging key in your codebase. IMPORTANT: variations is a JSON array where each object requires variant_key, is_active, and is_control fields. Exactly one variation must have is_control: true. Example variations: [{"variant_key": "control", "name": "Control", "is_active": true, "is_control": true}, {"variant_key": "treatment", "name": "Treatment", "is_active": true, "is_control": false}]. IMPORTANT: metrics is a JSON array of objects with metric_id (integer) and is_primary (boolean) fields. Exactly one metric must have is_primary: true. Example metrics: [{"metric_id": 333870, "is_primary": true}]. Dates must be ISO 8601 format: 2024-01-01T00:00:00Z. See the documentation