Oviond

Update theme

update_theme

Update a theme — only include the fields you want to change. Supply the full tokens map when changing visual properties (partial token updates replace the entire map). Update cover_page or thank_you_page to change the chosen background images. Flip is_default true/false to manage the account default (only one default per account).

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Theme ID (from list_themes)
`name`	No	Theme name
`tokens`	No	Complete token map — replaces the entire stored token set. Include all tokens when updating visual properties.
`cover_page`	No	Cover-page configuration: background image URL plus title and subtitle overlays (variable-substituted at render time).
`is_default`	No	Mark/unmark this theme as the account default
`thank_you_page`	No	Thank-you-page configuration: background image + title + subtitle.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	The theme as saved — id, name, tokens and page config.
`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 theme as saved — id, name, tokens and page config.",
+      "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.4/5.0

Behavior4/5

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

With annotations already signaling readOnlyHint=false and destructiveHint=false, the description adds valuable behavioral nuance: partial token updates replace the entire token map, and only one default is allowed per account. These are non-obvious side effects not captured by the annotations or schema fields alone, making the tool safer to invoke correctly.

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 three focused sentences, each with a clear purpose: the first states the update behavior and partial-update rule, the second warns about token-map replacement, and the third covers cover/thank_you and is_default. No redundancy or filler; it is front-loaded with the most critical usage guidance.

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 6-parameter update tool with a rich schema and an output schema, the description covers the key behavioral pitfalls (token map replacement, default constraint, page background update) while leaving detailed parameter documentation to the schema, which is present. It is complete enough for an agent to call the tool correctly without additional context.

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 the baseline is 3. The description adds extra meaning by stating the partial-update rule ('only include the fields you want to change') and the token-map replacement caveat, which are not fully communicated by the schema descriptions alone. It also reinforces which parameters to use for specific visual changes, going beyond simple schema repetition.

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 opens with 'Update a theme', a specific verb+resource, and immediately clarifies the partial-update behavior ('only include the fields you want to change'). This distinguishes update_theme from create_theme and archive_theme and tells an agent exactly what the tool does.

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 explicit usage guidance for tokens, cover/thank_you_page, and is_default, including the constraint that only one default exists per account. It does not explicitly name sibling alternatives or say 'instead of create_theme', but the context of an update operation and the partial-update rule provides clear context for when to use it.

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?