Adverity MCP tools
On this page
This reference lists the tools that Adverity MCP provides to your AI assistant. For an introduction to Adverity MCP and how write actions are confirmed, see Using Adverity MCP.
Available MCP tools
The MCP server provides 41 tools organized by domain. Each resource has a separate tool for reading, for writing, and — where the resource can be deleted — for deleting, so no tool both reads and changes your data. Most tools that filter, create, or update within a workspace take its numeric workspace_id — the same id returned by workspace_search’s list action — as the primary identifier; older stack_id and workspace_slug parameters, where a tool still exposes them, continue to work as aliases. The tag, monitor, and user tools identify workspaces, datastreams, and users by UUID instead.
How the tools are named
Almost every tool name says what it does to your data:
*_searchReads only. Never changes anything.
*_writeChanges data: creates, updates, or acts on a resource, such as
fetch_writetriggering and stopping fetches. Some resources name this tool after the operation instead, such aserror_resolve,extract_requeue, andmonitor_assign.*_deleteRemoves something. Often irreversible: see the note on each tool below for what a specific delete takes with it.
Three read-only tools predate the convention and keep their original names: get_warehouse_schema, query_warehouse, and read_docs.
Each tool also declares to your AI assistant whether it only reads data or can destroy it. Every *_delete tool declares itself destructive, and so do the write tools whose worst case is destructive: authorization_write, fetch_write, destination_write, data_mapping_write, user_write, error_resolve, extract_requeue, monitor_write, monitor_assign, and universal_monitor_write. Most AI assistants use that declaration to run read tools without interrupting you and to ask before running a destructive one, though the behavior depends on the client and on the tool permissions you have set. The confirmation step applies either way.
Tool catalogue
Tool actions that create, change, or delete data ask for confirmation first. For details, see Confirmation for write actions.
datastream_search,datastream_write,datastream_deleteCore tool for pipeline management and troubleshooting, capable of:
Listing, creating, configuring, and deleting datastreams
Viewing status, enabling or disabling pipelines, and filtering the datastreams that are scheduled for deletion
Duplicating a datastream, including its source columns, schedules, and target bindings
Viewing a datastream’s dashboard KPIs
Exploring available connector types and their field options
Reading and editing a datastream’s configured fields (the metrics and dimensions it collects) to add or remove columns without leaving your AI assistant
Listing the transformations applied to a datastream, and attaching or detaching a transformation
datastream_tag_search,datastream_tag_write,datastream_tag_deleteOrganizes datastreams with tags. List the tags in a workspace, list datastreams with their tags and filter them by tag, and read the tags of many datastreams at once. Create and rename tags, and assign or unassign up to 50 tags across up to 500 datastreams in one step. Assigning can create tags that do not exist yet. Creating, renaming, assigning, unassigning, and deleting a tag require explicit confirmation. For more information about tags, see Tagging datastreams in Connect API.
authorization_search,authorization_write,authorization_deleteManages authorizations for connected data sources (Google Ads, Facebook Ads, LinkedIn Ads, etc.). List every authorization in a workspace across all connection types in one call, or filter to a single type. Create new connections, check whether a connection is currently authorized, handle OAuth flows, manually update stored OAuth tokens, and refresh metadata from external APIs. Generate connection-invite links so someone else can authorize a connection on your behalf. Also manages which accounts an authorization is permitted to collect from — list, enable, or disable specific permissions and control the grant-all flag. Creating, updating, or deleting an authorization, updating its OAuth tokens, refreshing its metadata, generating an invite, and updating permissions or the grant-all flag all require explicit confirmation. Getting the OAuth URL to re-authorize a connection does not. Generating an invite emails the invitee unless you ask the assistant not to. Essential for preventing pipeline failures.
fetch_search,fetch_write,fetch_schedule_deleteControls data collection jobs. Trigger fetches on demand or for a specific date range, monitor job status and import status, stop a running job, and retry a failed job within its existing job group. Triggering for a date range runs the scheduled fetches that fall in that range; a fixed-range fetch collects exactly the dates you give.
Each datastream collects data either on a schedule or with smart pulling. You can see which mode is active, switch between the two, and configure smart pulling here. You can also list a datastream’s schedules and delete a single schedule. On a datastream that uses schedules, change a schedule through
datastream_write; on one that uses smart pulling, change its configuration here. Critical for troubleshooting and managing data collection.monitor_search,monitor_write,monitor_delete,monitor_assignManages custom data-quality monitors. List monitors with their rules and the datastreams they watch, the monitors given datastreams can take, and the operators and columns a rule can use. Create and update monitors, delete them, and assign or unassign datastreams: to one monitor, or several monitors to a selection of datastreams.
universal_monitor_search,universal_monitor_writeReads and configures the four universal monitors every datastream has: row duplicates, volumes, timeliness and schema consistency. Read one datastream's monitors, list one monitor type across datastreams (optionally only enabled or disabled ones, or one severity), and read or preview the schema-consistency baseline. Configure one datastream's monitor, switch a type on or off or set its severity across many datastreams, or replace the baseline schema.
error_search,error_resolveLists errors and their state, retrieves details for a single error by ID, retries failed operations, and acknowledges errors. Listing returns only errors that have not been acknowledged, unless you ask for acknowledged ones too. Retry and confirm actions require explicit confirmation and can be applied to a single error or to every error in the same error group. Before retrying a single error, the tool checks that its job can be retried, so it does not use up your data source quota on a retry that cannot succeed.
extract_search,extract_requeueLists and downloads data extracts from successful datastream executions. Download a specific extract or the latest one for a datastream; downloads return a preview of the first rows by default, and you can request the full content when you need the complete file. Read an extract’s stored metadata or its row data, and re-import existing extracts to their destinations without re-fetching the source data.
workspace_search,workspace_writeLists workspaces, shows their structure and hierarchy, lists available storage locations, and shows a workspace’s dashboard KPIs. Also creates and updates workspaces. Creating a workspace needs a name and a storage location, so the assistant lists the available storage locations first. Updating can rename a workspace, change its storage, move it under another parent workspace, and change its other settings. Useful for multi-workspace environments. Creating or updating a workspace requires explicit confirmation. Workspaces cannot be deleted through MCP.
transformation_search,transformation_write,transformation_deleteCreates, lists, and edits transformations as part of datastream setup, and retrieves the schema of supported processing operations. Creating a transformation does not apply it to a datastream: the assistant attaches it in a second step with
datastream_write. Only the name and description of a transformation can be edited after creation. Creating, updating, and deleting a transformation each require explicit confirmation.mapping_table_search,mapping_table_write,mapping_table_entry_deleteLists, retrieves, and updates mapping tables used for data harmonization. Manages individual mapping table entries — add, edit, or delete match-to-value pairs. All write operations require explicit confirmation because changes affect data harmonization for every datastream that uses the table. Read-only access to value tables — a separate reference resource used by transformations — is also available.
data_mapping_search,data_mapping_write,data_mapping_deleteMaps a datastream’s source columns to target columns — the Data Mapping step that controls which harmonized field each incoming column populates. List source and target columns, view a connector type’s default mapping, create new target columns, and map, unmap, bulk-replace, or copy a datastream’s column mappings from another datastream of the same connector type. Also lists, sets, and removes a connector type’s default mappings, which decide how newly discovered columns are mapped. All write and delete operations require explicit confirmation.
New target columns are created for the whole instance, with one of these data types: String, Long, Float, Date, DateTime, Boolean, Percentage, Currency, JSON, Formula, or Duration. A metric also takes an aggregation:
SUM,AVG,COUNT,MIN,MAX, orNONAGG.destination_search,destination_write,destination_deleteCreates and manages destinations — where harmonized data is delivered (BigQuery, Snowflake, Google Sheets, etc.). List available destination types and the fields each type requires, configure destinations, and manage which datastreams load into each destination, including whether each one is enabled and which table it writes to. Each destination type has its own required fields, so the assistant reads them before creating a destination. Creating, updating, and deleting a destination or a datastream assignment require explicit confirmation. The assistant does not ask for destination credentials in the chat; it sends you to enter them on the destination page in Adverity.
To control which source column populates which field, use
data_mapping_write.user_search,user_write,user_deleteLists and manages instance users (identified by UUID). List users, retrieve a single user, and create, update, or delete users. Any assignable platform role can be set — see Managing user permissions. Creating, updating, and deleting a user require explicit confirmation.
notification_search,notification_write,notification_deleteManages notification subscriptions across email, Slack, Microsoft Teams, and webhook channels. List, retrieve, create, update, and delete subscriptions, optionally scoped to specific datastreams or workspaces. Creating, updating, and deleting a subscription require explicit confirmation.
Each channel needs different details:
A recipient email address that belongs to an existing Adverity user, and one or more notification topics.
- Slack
An incoming webhook URL and one or more notification topics. A channel name is optional.
- Microsoft Teams
An incoming webhook URL only. Topics and channel names are not supported.
- Webhook
The URL to send events to, and one or more event names. You can store a signing secret, but payloads are not signed yet.
A new subscription does not send a test message. It fires the next time a matching event happens, such as a fetch job failing.
get_warehouse_schemaQueries the schema: lists the columns Adverity has loaded into a workspace’s warehouse, scoped to that workspace’s own tracked data. Call this before running a query to see what’s available.
query_warehouseInterrogates the data: runs a read-only SQL query (
SELECTorWITHonly) against a workspace’s warehouse and returns the results. Results are capped at 100 rows and time out after 45 seconds — write narrow, aggregated queries rather than ones that scan everything. Any statement other thanSELECT/WITHis rejected before it reaches the warehouse. Queries on the facts view are also rejected if they useSELECT *or do not filter on a date column.read_docsAnswers questions about Adverity from the official documentation at docs.adverity.com. The default search mode returns short excerpts with links back to the source page; an alternative mode returns a synthesised written answer with its sources. A third mode returns Adverity’s implementation guides for specific connectors and topics. Read-only, with no confirmation required.