GoodBarber

Create video

cms_create_video

Create video item. Guidance: Create one CMS video item from video category ids. | context: title, categories, embedUrl

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": {
      "title": "<title>",
      "categories": "<categories>",
      "embedUrl": "<embedUrl>"
    },
    "name": "cms_create_video"
  }
}

Input Schema

Name	Required	Description
`date`	No	Optional editorial date in RFC 3339 format.
`meta`	No	Optional SEO payload with title and description.
`slug`	No	Optional URL slug; the server may normalize it.
`title`	Yes	Video headline shown in feeds and on the item page.
`author`	No	Optional byline or author display name. If omitted, the app account holder's name is used.
`leadin`	No	Optional Summary field in the back-office Info panel (deck / chapo), as plain text. 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	Whether the video is pinned in its category listing.
`status`	No	Publication status. Omit on create to default to published. Do not send scheduled.
`embedUrl`	Yes	Video player iframe or embed HTML; non-empty. Set an explicit iframe width and height (for example 100%) so the player renders at a visible size.
`accessTier`	No	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`	Yes	Non-empty category id array. Use cms_list_cms_sections with type='video' to discover video category ids.
`publishedDate`	No	Future ISO datetime for deferred publication. Requires status='stock' when provided.
`commentsEnabled`	No	Whether end-user comments are enabled for this video.
`publicationEndDate`	No	Future ISO datetime for 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=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds no behavioral detail beyond that: nothing about non-idempotency/duplicate-creation risk on retry, the default published status, or side effects—all of which live in the schema rather than the description.

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?

It is short and front-loaded, but the two sentences are redundant ('Create video item' vs. 'Create one CMS video item from video category ids'), and the trailing '| context:' fragment is an awkward, low-information appendage.

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 14-parameter creation tool with nested objects, enums and idempotentHint=false, yet the description does not address duplicate-creation risk, the publish/stock interplay, or what a successful creation returns. It relies almost entirely on the schema and annotations.

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%, so the baseline is 3; the schema already explains status defaults, the stock requirement for publishedDate, accessTier semantics and category discovery. The description only echoes the three required fields ('title, categories, embedUrl') and adds no meaning beyond the schema.

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?

'Create video item' names a concrete verb and resource, and the second sentence clarifies it creates a single CMS item from category ids. It is understandable but adds little beyond the name and title, with no differentiation from the neighboring create_*_paragraph or cms_create_article tools.

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 'Guidance' line merely restates the action ('Create one CMS video item from video category ids') rather than saying when to choose this tool over cms_create_video_paragraph or cms_update_video. No prerequisites, no when-not-to-use, no alternatives are named.

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.