Oviond

Add custom data widget

add_custom_data_widget

Add a Custom Data widget to a page: a table showing demo data until it points at an uploaded CSV dataset. Returns the new widget_id — configure it with update_data_widget, passing advanced.custom_data_id from list_custom_data plus the dataset's own column names as the metrics and dimensions (get_custom_data lists them). Position, width and height match the editor's Custom Data card.

Input Schema

TableJSON Schema

Name	Required	Description
`page_id`	Yes	Page ID the widget will be placed on, from list_pages.
`client_id`	Yes	Client ID the report belongs to (from list_clients).
`source_id`	Yes	Report ID the widget belongs to (from list_reports).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	The custom data widget, still on demo data until a dataset is picked, that was added — widget_id, plus the stored row with the defaults the server filled in (position, width, height).
`success`	Yes	True when the call succeeded. A failure comes back as an error result instead.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "The custom data widget, still on demo data until a dataset is picked, that was added — widget_id, plus the stored row with the defaults the server filled in (position, width, height).",
+      "type": "object"
+    },
+    "success": {
+      "description": "True when the call succeeded. A failure comes back as an error result instead.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedSep 18, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only indicate it is not read-only and not destructiveasi no contradiction. The description adds meaningful behavioral detail: the widget initially shows demo data, returns a new widget_id, and has position/size behavior matching the editor's Custom Data card. This goes beyond what the annotations reveal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded: it states the action, the initial state, the return value, and the follow-up configuration steps in a tight, logical flow. Each sentence contributes necessary information without redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with only three required parameters and an output schema, the description covers the key context an agent needs: what the widget does initially, what the return value is, how to configure it next, and where to get the required IDs and column names. No crucial information is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for all three required parameters, each sourced from list_pages, list_clients, or list_reports. The tool description does not add extra parameter-level meaning, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Add a Custom Data widget to a page', and describes its behavior as 'a table showing demo data until it points at an uploaded CSV dataset.' This clearly distinguishes it from related sibling tools like add_data_widget or add_button_widget, which serve different widget types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear workflow context by explaining that the returned widget_id should be used with update_data_widget, and where to get advanced.custom_data_id and column names. It does not explicitly list exclusions or alternatives, but the focused purpose and follow-up configuration make the intended usage clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Oviond tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?