Oviond

Create report from template

create_report_from_template

Create a report or dashboard for an existing client by cloning a template (its pages + widgets). Find the template first with list_templates — filter by datasources + type (e.g. datasources=gadw, type=DASHBOARD for a Google Ads dashboard).

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Name for the new report
`type`	Yes	Report type — must match the template
`client_id`	Yes	Client id (from list_clients)
`template_id`	Yes	Template to clone (from list_templates — filter by datasources + type)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	The new report — its id, name and type, the template it was cloned from, and the client it belongs to.
`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": {
+      "description": "The new report — its id, name and type, the template it was cloned from, and the client it belongs to."
+    },
+    "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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so an agent knows this is a non-destructive mutation. The description adds value by disclosing that the operation clones the template's pages and widgets into a new report and requires an existing client. This is consistent with the annotations, with no contradiction.

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?

Two sentences, zero waste. The core action is front-loaded in the first sentence, and the second sentence earns its place by naming the prerequisite tool, the filter criteria, and a concrete example. Nothing redundant with the schema.

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

Completeness4/5

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

For a mutation tool with 4 documented parameters, an output schema, and a clear prerequisite workflow, the description is nearly complete. It covers the cloning behavior, the existing-client constraint, and the template discovery step. The only minor gap is not warning about type-matching failure, but the schema already states 'must match the template', so this is adequately covered.

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

Parameters4/5

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

Schema coverage is 100%, so each parameter is already documented. The description adds meaning beyond the schema by tying the workflow together — the template_id must come from list_templates filtered by datasources+type — and by giving a concrete example (datasources=gadw, type=DASHBOARD for a Google Ads dashboard) that clarifies how to select the right template.

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+resource ('Create a report or dashboard... by cloning a template') and the mechanism ('its pages + widgets'). This clearly distinguishes it from siblings like create_report (build from scratch), duplicate_report, and create_template, so an agent can tell them apart without opening schemas.

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 an explicit prerequisite workflow: 'Find the template first with list_templates — filter by datasources + type', including a concrete filter example. The context makes the intended use clear, though it does not explicitly exclude alternatives like create_report or duplicate_report.

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?