Skip to main content
Glama
srgplus

srgplus-mcp

Official
by srgplus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

add_content_to_categories

Adds a content item to specified categories within a channel. Requires content, channel, category, and workspace IDs.

Instructions

Add a content item to one or more channel categories.

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 inside that channel to add the content to

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/5.0
Behavior2/5

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

Annotations already provide readOnlyHint=false and destructiveHint=false, but the description adds no side-effect, permission, idempotency, or error behavior details. Transparency is limited to the basic mutation stated in the action.

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?

One-sentence purpose followed by a clean parameter list. No filler, redundancy, or unnecessary detail.

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?

The action and all parameters are sufficiently covered. Since an output schema is present, return-value details are not required, and no critical context is missing.

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 four required parameters are explained in the description, including a source hint for workspace_id and clarification that category_ids are scoped to the given channel. This adds substantial meaning beyond the bare schema.

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?

States a specific action: 'Add a content item to one or more channel categories', clearly identifying the resource and target. The plural 'one or more' distinguishes it from the sibling add_content_to_category tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for multi-category assignment via 'one or more', but it does not explicitly contrast with add_content_to_category or state when to prefer this tool over alternatives.

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