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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 25, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / properties / cover_page / properties / widgets
```
Removed value: -{
-  "items": {},
-  "type": "array"
-}
```
removedInput schema / properties / thank_you_page / properties / widgets
```
Removed value: -{
-  "items": {},
-  "type": "array"
-}
```

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedOutput schema / properties / success / description

Previous value: -"True when the call succeeded. A failure comes back as an error result instead."New value: +"True when the call succeeded."

First observedSep 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations mark it as non-read-only and non-destructive, so mutation is implied. The description adds behavioral details beyond annotations: partial token updates replace the entire map, and only one default per account. These behaviors are not visible in annotations and help the agent anticipate side effects. It does not contradict annotations.

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 four sentences, each adding distinct value: partial updates, token map behavior, cover/thank-you pages, and default management. It is front-loaded with the core action and wastes no words, making it easy to scan.

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?

With an output schema present, return format is covered. The tool has 6 parameters including nested objects, and the description explains how each major field behaves. It does not mention error cases or prerequisites, but the schema covers required id and id sourcing. Overall, sufficient for correct invocation.

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?

Schema coverage is 100%, so every parameter is already described in the schema. The description adds a few clarifications (e.g., full token map replacement, default uniqueness) but largely paraphrases the schema. Baseline 3 is appropriate because the schema carries the primary semantic load.

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 starts with 'Update a theme' — a specific verb and resource — and enumerates the fields that can be changed (tokens, cover_page, thank_you_page, is_default). It clearly differentiates from sibling update_* tools by focusing on theme-specific attributes and partial-update semantics, making its purpose unambiguous.

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 instructions on how to use the tool: include only fields to change, supply full token map for visual changes, update cover/thank_you pages for backgrounds, flip is_default. It does not explicitly name alternative tools, but the tool name and context make it obvious when to use it. It provides usage context without explicit exclusions.

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?