srgplus-mcp

Official

Overview Schema Source Related Servers Discussions Admin

move_subcontent

Reorder subcontent items in a collection section by specifying the item to move and the item it should follow, or place it first by passing null for the previous item ID.

Instructions

Reorder a subcontent item within a collection section.

Moves the item to the position immediately AFTER previous_subcontent_id.
Pass previous_subcontent_id=None to move the item to the very first
position in the section.

workspace_id: target workspace ID — get available IDs from list_workspaces()
content_id:             ID of the collection (the parent content item)
category_name:          "Content" or "Asset"
section_id:             ID of the section containing the subcontent item
subcontent_id:          ID of the subcontent item to reorder
previous_subcontent_id: ID of the item that should come directly before the
                        moved item; None places it first in the section

Input Schema

TableJSON Schema

Name	Required	Description	Default
`content_id`	Yes
`section_id`	Yes
`workspace_id`	Yes
`category_name`	Yes
`subcontent_id`	Yes
`previous_subcontent_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.18Sep 8, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations indicate a mutating operation (readOnlyHint false) that is not destructive (destructiveHint false) and an open world (openWorldHint true). The description adds the ordering mechanism but does not disclose potential side effects, permission requirements, or effects on other items. It does not contradict annotations, but given the open world hint, more transparency could be expected.

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

Conciseness4/5

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

The description is moderately sized with a clear first sentence and a structured parameter block. Each sentence adds value, and the core behavior is front-loaded. It is well-organized without excessive verbosity.

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?

Given the 6 parameters and the existence of an output schema, the description covers the behavior and parameters adequately. It does not address error handling or prerequisites, but the information needed to call the tool correctly is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero parameter descriptions, so the description is the sole source of meaning. It explains each parameter's role, provides guidance on obtaining workspace IDs from list_workspaces(), and clarifies the behavior of previous_subcontent_id. This fully compensates for the 0% coverage.

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 clearly states the action 'Reorder a subcontent item within a collection section,' specifying the verb, resource, and context. This distinctly separates it from sibling tools like add_subcontent, delete_subcontent, and get_subcontent, which operate on different aspects of subcontent.

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 explains how to use the tool, including the special case of previous_subcontent_id=None to place the item first. It provides clear operational context but does not explicitly contrast with alternatives like move_content, though the scope is evident from the naming and description.

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

Deploy Server