Manage tracking plan taxonomy
The product's event and property definitions are updated, created, or cleaned up in the tracking plan to ensure consistent data collection.
How it works
Changes data in your accountsSoftware development
The agent reads the current taxonomy using get_amp_taxonomy to understand existing events and properties. It then uses manage_amp_events or manage_amp_properties to create new definitions, update existing ones, or delete redundant items. The agent verifies that changes comply with the workspace's naming conventions and AI Context rules before executing write operations.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Prompt for Manage tracking plan taxonomy
Check the current taxonomy for any events named 'click_button'. If they exist, update them to follow the new 'user_action' naming convention. Also, create a new property 'button_id' for the 'click_button' event.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
Manage taxonomy: create, update, delete, and restore events and properties, manage tracking-plan branches, and read transformations and group types.Amplitude documentation