Skip to main content
Glama

Delete channel set

delete_channel_set
DestructiveIdempotent

Delete a saved channel set by ID. The set is removed without affecting its channels, freeing up organization. Use to discard unused channel groupings.

Instructions

Delete a channel set by ID. Does not affect the channels themselves. Use this when the user wants to remove a saved channel set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
setIdYesThe channel set ID to delete.
Install Server

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate destructive and idempotent behavior. The description adds a crucial behavioral detail beyond annotations: deleting the set does not affect the channels themselves. This prevents an agent from assuming cascading deletion, which is valuable 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 two concise sentences with no filler. The core action is front-loaded, followed by the clarifying scope caveat and a direct usage instruction. Every sentence contributes meaningful guidance.

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 single-parameter delete operation, the description covers what is deleted, what is not deleted, and when to use it. Combined with annotations for destructive and idempotent behavior, nothing essential is missing for an agent to invoke this tool correctly.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter setId is already described as 'The channel set ID to delete.' The description adds no additional semantic value beyond restating that deletion occurs by ID, so the baseline score of 3 is appropriate.

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 verb and resource: 'Delete a channel set by ID.' It further disambiguates by clarifying that channels themselves are unaffected, distinguishing this from tools that delete actual channels or media. The title and description align clearly.

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 explicitly says 'Use this when the user wants to remove a saved channel set,' providing clear context for when this tool is appropriate. It does not explicitly discuss exclusions or alternative tools, so it falls just short of top-tier guidance.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azeemkafridi/bulkpublish-api'

If you have feedback or need assistance with the MCP directory API, please join our Discord server