Skip to main content
Glama

Reorder video paragraphs

cms_reorder_video_paragraphs
Destructive

Reorder paragraphs. Guidance: Reorder all paragraphs for one CMS video item. | context: id, paragraph_ids

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVideo item id returned by cms_list_videos.
paragraph_idsYesFull ordered list of paragraph ids belonging to this video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

The description says 'Reorder all paragraphs,' which implies a full replacement of ordering and aligns with the destructiveHint annotation. It does not add significant behavioral detail beyond the annotations, but there is no contradiction.

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 compact and directly to the point, with no unnecessary wording. The parameter descriptions are also concise and informative.

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

Completeness5/5

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

For a simple reorder operation with two well-described parameters and no output schema, the description is complete. It covers what the tool does, the target resource, and the expected parameter semantics.

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?

Both parameters are described with helpful context: id is identified as returned by cms_list_videos, and paragraph_ids is clarified as the full ordered list belonging to the video. This goes beyond the basic schema and aids correct usage.

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 tool name and description clearly state it reorders paragraphs for a CMS video item, distinguishing it from sibling reorder tools for articles, events, maps, and sounds. The resource (video paragraphs) and action (reorder all) are specific.

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 provides clear context that this tool is for reordering all paragraphs of one CMS video item. It does not explicitly mention alternatives or exclusions, but the resource-specific wording makes the intended use unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.