Skip to main content
The Oviond MCP server exposes 151 tools across 25 groups. Most map to a single REST operation; a few chain several. Tool names are verb-first — create_client, list_reports, add_data_widget — so an agent can guess the right one from the action. Every tool also carries a title and read-only / destructive hints, so a client can show what a tool will do before it runs.

Tool catalog

Account

Archive

Assets

Automations

Branding

Calculated metrics

Clients

Company

Custom data

Datasources

Domains

Email

Exports

Folders

Goals

Media

Pages

PDF

Reports

Templates

Themes

Users

Widgets

Workflows

Conventions

  • Identifiers — calls return IDs the agent chains into later calls. It is instructed to refer to records by name in chat, never by ID.
  • Multi-tenancy — every call is scoped to the authenticated account. You never pass an account_id.
  • Discovery first — datasources, then describe_datasource, before configuring a data widget: the second returns that datasource’s data views, metrics, dimensions and required settings.
  • Metrics and dimensions are objects — pass [{ "value": "clicks" }], not ["clicks"]. Only value is required; Oviond fills in the rest from the catalog. The same shape is used by the widget, goal and calculated-metric tools.
  • One tool per widget type — add_data_widget for a datasource-backed widget, and add_calculated_metric_widget, add_custom_data_widget, add_goal_widget and add_static_value_widget for the four sources that aren’t a platform. Each takes only the fields its type has, and each has a matching update_ tool.
  • Data is fetched server-side after a widget is written. refresh_widgets or refresh_report force it. Reading it back is get_widget_data, which waits briefly for in-flight fetches and returns each widget’s state plus its rows — up to 200 per widget.
  • query_data is the read-only way to pull figures. It returns live metric values for any date range straight from the client’s connected datasource and saves nothing, so it works on a read-only connection — unlike refresh_widgets, which writes the results back onto the report and a read-only client will rightly decline. Use get_widget_data to read what a report already holds, and query_data for ad-hoc analysis and period comparisons.

Reference

Each tool wraps an Oviond REST operation. For exact parameters and response shapes, see the API Reference.