Oviond

Update account branding

update_branding

Update branding settings — only include the fields you want to change. For logo_url and favicon_url, use list_media to look up a URL from uploaded media. (Brand color is no longer configurable — theming is per-report.)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`logo_url`	No	Logo URL (use list_media to find an uploaded image URL)
`favicon_url`	No	Favicon URL (use list_media to find an uploaded icon URL)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	The branding as saved — logo_url and favicon_url.
`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 branding as saved — logo_url and favicon_url.",
+      "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/5.0

Behavior4/5

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

Annotations already convey readOnlyHint=false and destructiveHint=false McDonald's the safety profile. The description adds behavioral context beyond annotations: partial-update semantics ('only include the fields you want to change') and a legacy constraint ('Brand color is no longer configurable — theming is per-report'). No contradiction with 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?

Three concise sentences, front-loaded with the key behavior (partial update), then the prerequisite for parameter values, then the deprecated field note. Every sentence earns its place and there is no fluff.

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?

The tool is simple with only two optional paramsley and no required fields. The description covers how to use it, the URL requirement, and what is no longer configurable. Combined with the output schema and annotations, this is nearly complete; only a explicit statement about what happens when no fields are provided is missing, but it is implied.

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 description coverage is 100% – both logo_url and favicon_url already describe the list_media hint. The description restates this hint and adds the partial-update behavior, but provides no additional per-parameter meaning beyond the schema, so baseline 3 is appropriate.

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

Purpose4/5

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

States a specific verb and resource ('Update branding settings'), so an agent knows the tool mutates account branding. It does not explicitly differentiate from siblings like get_branding or update_company, but the resource is unambiguous and the verb distinguishes it from read-only operations.

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?

Provides clear context: use partial updates ('only include the fields you want to change') and a precondition for parameter values ('use list_media to look up a URL from uploaded media'). It also excludes brand color and points to per-report theming, though it does not name the sibling tool that handles theming.

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?