:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Data discovery: After the metric check, before any analytical call that touches
collected data (query-*, execute-sql against events/persons/sessions), confirm
the event/property exists via call read-data-schema. Applies to canonical-looking names like $pageview too — they vary
per team. If the event isn't in the schema, tell the user instead of querying a guessed name.
Always run info read-data-schema first — the recipes below are common cases, not the full schema.
- Events:
call read-data-schema {"query": {"kind": "events"}}(paginate withlimit/offsetif needed). Actions come fromactions-get-allinstead. - Event properties:
call read-data-schema {"query": {"kind": "event_properties", "event_name": "<event>"}} - Person, session, and group properties:
call read-data-schema {"query": {"kind": "entity_properties", "entity": "<entity>"}}(entityisperson,sessionfor the columns of thesessionstable, or a group type name) - Values:
call read-data-schema {"query": {"kind": "event_property_values", "event_name": "<event>", "property_name": "<prop>"}}