AI Metadata Enrichment docs - #193
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Confidence Score: 4/5The outstanding MCP inventory mismatch should be fixed before merging so users can discover and verify the newly advertised tool. The feature documentation names Files Needing Attention: docs/data-governance/ai-powered-data-governance.mdx and docs/mcp.mdx
|
| Filename | Overview |
|---|---|
| changelogs.mdx | Adds a release announcement describing automated event metadata enrichment. |
| docs/data-governance/ai-powered-data-governance.mdx | Documents the enrichment workflow, but its advertised MCP tool remains absent from the canonical tool inventory. |
Reviews (4): Last reviewed commit: "Merge branch 'main' into update-docs-ai-..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| - **Keep what you wrote**: Enrichment only fills gaps. Events with an existing display name or description keep what you gave them. | ||
| - **See what changed**: Every enriched field is recorded in the event's history, attributed to the user who ran the fill, marked as AI-applied, and written to your audit log like any other Lexicon edit. | ||
|
|
||
| The same fill is available to agents over MCP via the Fill-Event-Metadata tool and inside Mixpanel Agent. |
There was a problem hiding this comment.
When users consult the MCP reference to discover the advertised Fill-Event-Metadata tool, the canonical tool inventory omits it, preventing them from discovering or confirming the documented enrichment workflow.
Knowledge Base Used: Developer platform and automation
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
|
|
||
| ## Automated Metadata Enrichment | ||
|
|
||
| Raw event names rarely explain themselves. btn_clk_add_crt means something to the engineer who instrumented it and little to anyone else, including Mixpanel Agent and MCP, which rely on Lexicon to understand your data. Writing a display name and description for every event takes time, so most projects have gaps. Mixpanel can now fill them for you. |
There was a problem hiding this comment.
Can we wrap btn_clk_add_crt in ` so that it appears more distinct from the plain text? Otherwise looks good to me!
2 participants
Update AI Powered Data Governance documentation with the new AI Metadata Enrichment feature