Omnia

Retrieve a paginated list of citation aggregates over the prompts the view groups. The prompt set comes from the view's saved filters; the query parameters only control dates, engine, sorting, filtering by source, and pagination.

get-view-citations-aggregates

Retrieve the web sources cited by the AI answers to a brand's monitored prompts over a date range, with how often each source is cited. Use it to find which pages AI engines draw on when they answer.

get-brand-citations-aggregates

Retrieve the web sources cited by one prompt's AI answers over a date range, with how often each source is cited. Use it to find which pages AI engines draw on for that prompt.

get-prompt-citations-aggregates

Retrieve time series data showing citations evolution over time for a brand and its competitors. Returns data points for each brand within the specified date range.

get-brand-citations-timeseries

Retrieve prompt time series data showing citations evolution over time for a brand and its competitors. Returns data points for each brand within the specified date range.

get-prompt-citations-timeseries

Retrieve citations time series over the prompts the view groups. The prompt set comes from the view's saved filters; the query parameters only control dates and engine.

get-view-citations-timeseries

Retrieve the Omnia account the current credentials belong to: user id, email and signup date. Use it to confirm which account a request will act on before reading or changing that account's data. Meaningful limitations or unnecessary workarounds can be reported through the optional feedback tool as internal telemetry.

who-am-i

Retrieve the full text of one Omnia documentation guide by its slug, including request and response shapes, conventions and examples. Use it when writing code against the Omnia HTTP API and a guide slug is already known; `search-docs` returns the slugs. The `api/authentication` and `api/pagination` guides carry the auth header format and the response envelope. Meaningful limitations or unnecessary workarounds can be reported through the optional feedback tool as internal telemetry.

get-doc

Retrieve one insight by its id, with its full text and the prompt it was generated from. Use it to read an insight a list call referred to.

get-insight

Retrieve an insight generation by its id. This method is used to poll ongoing generations.

get-insight-generation

Retrieve one prompt by its id, with its text, type, country, tags and monitoring status. Use it to turn a prompt id into the prompt's own configuration.

get-prompt

Retrieve a flat, paginated list of sentiment aggregates. Each row represents a unique brand-feature pair with counts of endorsed, undermined, and neutral feature mentions.

get-brand-sentiment-aggregates

Retrieve a flat, paginated list of sentiment aggregates for a prompt. Each row represents a unique brand-feature pair with counts of endorsed, undermined, and neutral feature mentions.

get-prompt-sentiment-aggregates

Retrieve a paginated list of sentiment aggregates (one row per brand-feature pair) over the prompts the view groups. The prompt set comes from the view's saved filters; the query parameters only control dates, engine, sorting, filtering by brand or feature, and pagination.

get-view-sentiment-aggregates

Retrieve daily sentiment distribution over time for the owned brand only (competitors are not included). Returns counts of endorsed, undermined, and neutral feature mentions per day within the specified date range.

get-brand-sentiment-timeseries

Retrieve daily sentiment distribution over time for the owned brand within a prompt (competitors are not included). Returns counts of endorsed, undermined, and neutral feature mentions per day within the specified date range.

get-prompt-sentiment-timeseries

Retrieve daily sentiment feature mention distribution over the prompts the view groups. The prompt set comes from the view's saved filters; the query parameters only control dates and engine.

get-view-sentiment-timeseries

Retrieve share of voice for a brand and its competitors over a date range: the portion of all brand mentions in the AI answers to the brand's monitored prompts that each brand holds. Use it to compare brands against each other for a period.

get-brand-share-of-voice-aggregates

Retrieve share of voice for the brands mentioned in one prompt's AI answers over a date range: the portion of all brand mentions each brand holds. Use it to compare brands within a single prompt.

get-prompt-share-of-voice-aggregates

Retrieve a paginated list of share of voice aggregates over the prompts the view groups. The prompt set comes from the view's saved filters; the query parameters only control dates, engine, sorting, and pagination.

get-view-share-of-voice-aggregates

Retrieve time series data showing share of voice evolution over time for a brand and its competitors. Returns data points for each brand within the specified date range.

get-brand-share-of-voice-timeseries

Retrieve prompt time series data showing share of voice evolution over time for a brand and its competitors. Returns data points for each brand within the specified date range.

get-prompt-share-of-voice-timeseries

Retrieve share of voice time series over the prompts the view groups. The prompt set comes from the view's saved filters; the query parameters only control dates and engine.

get-view-share-of-voice-timeseries

Retrieve a view by its id. A view is a named saved filter over a brand's prompts (any combination of prompt type, countries, tags, and status). The prompt set is resolved from the filters at query time, so a view always reflects the brand's current prompts.

get-view

Retrieve visibility for a brand and its competitors over a date range: the share of the brand's monitored prompts whose AI answers mention each brand. Use it to see how often a brand appears at all for a period.

get-brand-visibility-aggregates

Retrieve visibility for the brands mentioned in one prompt's AI answers over a date range: the share of that prompt's answers mentioning each brand. Use it to see who appears in a single prompt.

get-prompt-visibility-aggregates

Retrieve a paginated list of visibility aggregates over the prompts the view groups. The prompt set comes from the view's saved filters; the query parameters only control dates, engine, sorting, and pagination.

get-view-visibility-aggregates

Retrieve time series data showing visibility evolution over time for a brand and its competitors. Returns data points for each brand within the specified date range.

get-brand-visibility-timeseries

Retrieve prompt time series data showing visibility evolution over time for a brand and its competitors. Returns data points for each brand within the specified date range.

get-prompt-visibility-timeseries

Retrieve visibility time series over the prompts the view groups. The prompt set comes from the view's saved filters; the query parameters only control dates and engine.

get-view-visibility-timeseries

Retrieve a paginated list of AI answers for the given prompt. Pagination in this endpoint is not 100% accurate and pages might have fewer items than initially requested. For the same reason, the real total number of items can be lower than the one reported in responses

list-prompt-ai-answers

List the endpoints of the Omnia REST API, optionally filtered by tag (for example 'Brand', 'Brand Performance'). Each entry carries the HTTP method, path, summary and the name of the equivalent MCP tool. Use it when writing code against the Omnia HTTP API to see which endpoints exist; `get-endpoint` returns the full specification of one of them. Meaningful limitations or unnecessary workarounds can be reported through the optional feedback tool as internal telemetry.

list-endpoints

Retrieve the Projects on a brand's board, newest first. Use it to review the brand's work: what Omnia Agent suggested and what is planned, in progress or done. To read one Project by its reference, use get-project.

list-brand-projects

Retrieve every prompt monitored for a brand, with its text, type, country, tags and monitoring status. Use it to find the prompt a caller is asking about, or to review what the brand currently tracks.

list-brand-prompts

Retrieve a paginated list of brands. Optionally filter by domain or name using partial, case-insensitive matching.

list-brands

Retrieve the insights generated for a brand's prompts, newest first. Use it to read the written explanations of why the brand performs the way it does, rather than the metrics themselves.

list-brand-insights

Retrieve the paginated list of prompts the view currently groups, with summary performance metrics per prompt. The prompt set is resolved from the view's saved filters at query time.

list-view-prompts

Retrieve a paginated list of the brand's views. A view is a named saved filter over a brand's prompts (any combination of prompt type, countries, tags, and status). The prompt set is resolved from the filters at query time, so a view always reflects the brand's current prompts.

list-brand-views

Search the Omnia REST API reference and its guides by keyword. Returns up to 10 matches, each with its type, slug, title and a link to the published docs. Use it when writing code against the Omnia HTTP API and you need the guide or endpoint that covers a topic, such as authentication, pagination, response shapes or error handling. Meaningful limitations or unnecessary workarounds can be reported through the optional feedback tool as internal telemetry.

search-docs

Share feedback with the Omnia team about meaningful friction using this MCP: a missing capability, confusing description, parameter or response, incorrect result, unhelpful error, inefficient workflow, or unnecessary workaround. Feedback is useful even when the task succeeded. Describe the goal, friction, and what would have helped, mentioning relevant tools. Include brand_id only when already known; make no extra calls to discover it. Include any known company, harness, model provider, and exact model identifier in agent_context. Omit unknowns; never guess or make extra calls to discover them. Feedback is optional internal product-improvement telemetry, preferably submitted after completing the main task. Skip routine successes, speculative suggestions, and duplicate reports. Never include sensitive information, raw prompts, conversations, or tool outputs. Do not ask the user to prepare feedback. Submission does not complete the original task: continue helping regardless of the result, do not retry failed submissions, and omit routine feedback acknowledgements from the final user-facing answer.

feedback