Skip to main content
Glama
srgplus

srgplus-mcp

Official
by srgplus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

move_content

Move content to a different category within a channel by specifying workspace, content, channel, category, and section IDs.

Instructions

Move a content item to a different category section within a channel.

workspace_id: target workspace ID — get available IDs from list_workspaces()
content_id:  ID of the content item to move
channel_id:  ID of the channel containing the target category
category_id: ID of the destination category
section_id:  ID of the destination section within that category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
content_idYes
section_idYes
category_idYes
workspace_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.18

TDQS

A3.7/5.0
Behavior2/5

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

The description does not disclose behavioral details beyond the move action itself, such as whether the content is removed from its previous category/section or any side effects. Annotations cover readOnly and destructive hints, but the text adds no further behavioral context.

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 concise: a single clear action sentence followed by a short parameter list. There is no redundant or extraneous information.

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 description covers the action and all parameters, and an output schema exists, so return value details are not required. It is slightly limited by not explaining source/destination relationships or usage conditions, but it is otherwise complete for the operation.

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?

All five parameters are individually described in the description, including their roles and source hints such as 'get available IDs from list_workspaces().' Since the schema itself has no parameter descriptions, this fully compensates and adds clear meaning.

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 states a specific action: 'Move a content item to a different category section within a channel.' This clearly distinguishes it from sibling tools like move_subcontent or add_content_to_category by specifying the resource type and destination.

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 description gives parameter guidance but does not explicitly state when to use this tool versus alternatives such as add_content_to_category or remove_content_from_categories. It lacks direct 'use when' or 'not for' instructions.

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

Deploy Server

Other Tools