GoodBarber

Update video

cms_update_video

DestructiveIdempotent

Update video item. Guidance: Update one CMS video item by video id. | context: id

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "cms_update_video"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Video item id returned by cms_list_videos.
`date`	No	Omit to keep the current editorial date; send RFC 3339 to replace it.
`meta`	No	Optional SEO payload with title and description.
`slug`	No	Omit to keep the current slug; send to replace it.
`title`	No	Omit to keep the current headline; send to replace it.
`author`	No	Omit to keep the current byline; send to replace it.
`leadin`	No	Summary field in the back-office Info panel (deck / chapo), as plain text. Omit to keep it; send an empty string to clear it. HTML tags and text after a bare less-than sign are stripped server-side. The summary response field is a read-only computed excerpt.
`pinned`	No	Omit to keep the current pinning state; send true or false to replace it.
`status`	No	Omit to keep the current publication state. Do not send scheduled.
`embedUrl`	No	Omit to keep the current player; send new iframe or embed HTML to replace it. Set an explicit iframe width and height (for example 100%) so the player renders at a visible size.
`accessTier`	No	Replacement paywall tier. 'premium' locks the item behind an in-app purchase; 'free' leaves it open. Applies only to apps that sell in-app purchases.
`categories`	No	Omit to keep placement. Send non-empty category ids to replace placement.
`publishedDate`	No	Future ISO datetime for deferred publication. Requires status='stock' when provided.
`commentsEnabled`	No	Omit to keep the current comments setting; send true or false to replace it.
`publicationEndDate`	No	Future ISO datetime for scheduled unpublication. Send an empty string to clear an existing scheduled unpublication.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026
RemovedOct 8, 2026
First observedSep 8, 2026

TDQS

C2.5/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is known. The description adds nothing on top of that: it does not explain the partial-update contract (omitted fields are preserved), that the operation is destructive, or any permission or rate-limit implications. Consequently, the description contributes no behavioral value beyond the annotations.

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

Conciseness3/5

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

The description is short, but it is not concise in any useful sense: the first sentence duplicates the second and the name, and the trailing "| context: id" fragment is template boilerplate rather than front-loaded information. The wording is brief, yet it repeats itself instead of prioritizing useful content.

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

Completeness2/5

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

This is a destructive 15-parameter mutation with a nested object and no output schema, so the description should carry more weight. Instead it says essentially nothing about the fields, the partial-update semantics, the status/publishedDate coupling, or what is returned. An agent can only proceed by reading the schema in full.

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% and all 15 parameters, including the nested meta object and both enums, are documented in the schema with omit-to-keep semantics. The description adds no parameter meaning whatsoever, so the baseline 3 for fully documented schemas applies.

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

Purpose3/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 ("Update one CMS video item by video id"), but the first line "Update video item." merely restates the tool name and title, and the second line adds only the lookup key. There is no differentiation from cms_update_video_paragraph or the other cms_update_* siblings, and no indication of which fields can be changed.

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

Usage Guidelines2/5

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

The line labelled "Guidance" contains no actual guidance: it only restates that one item is updated by id. There is no when-to-use versus when-not, no mention of preferring cms_update_video_paragraph for paragraph-level edits, and no prerequisites such as obtaining the id from cms_list_videos (that is only in the schema).

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

All GoodBarber 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.