Skip to main content
Glama
srgplus

srgplus-mcp

Official
by srgplus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

remove_content_from_categories

Destructive

Remove a content item from specified channel categories without deleting it. Provide workspace, content, channel, and category IDs to update category assignments.

Instructions

Remove a content item from one or more channel categories.

The content item itself is not deleted.
workspace_id: target workspace ID — get available IDs from list_workspaces()
content_id:   ID of the content item
channel_id:   ID of the channel
category_ids: IDs of the categories to remove the content from

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
content_idYes
category_idsYes
workspace_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.18

TDQS

A4.4/5.0
Behavior4/5

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

The description adds useful behavioral context beyond the annotations, notably that the content item itself is not deleted. The destructiveHint annotation already signals mutation, and the description clarifies the scope of the destruction without contradicting 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.

Conciseness5/5

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

The description is concise, well-structured, and front-loaded with the core purpose. The important non-deletion clarification is included immediately, and the parameter list is clean and easy to scan.

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?

For a relatively simple operation, the description covers the essential context: the action, the affected resource, and a key side-effect clarification. Since an output schema is present, the lack of return-value explanation is acceptable. It does not mention error conditions or relationship constraints, but these are not critical for this straightforward operation.

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?

All four required parameters are mentioned and given at least basic semantic meaning. The workspace_id parameter includes a helpful source hint (list_workspaces()). The other parameter explanations are simple but adequate, adding mild value over the raw schema names.

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 ('Remove') and the resource ('a content item from one or more channel categories'). It is unambiguous and immediately distinguishes this operation from deleting the content itself, which is reinforced by the follow-up sentence.

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 useful context by clarifying that the content item is not deleted, helping the agent understand when this operation is appropriate versus a destructive content removal. However, it does not explicitly name alternatives such as archive/delete or the add-content-to-category counterpart.

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