Skip to main content
Glama

category_collection_update

Update a category or collection by adding or removing specific patterns or categories, without replacing the entire list.

Instructions

Update category or collection incrementally.

Add or remove individual patterns (for categories) or category references (for collections) without replacing the entire list. For complete property replacement, use category_collection_change.

Arguments

  • type (required): enum: 'category', 'collection'

    • Type of item to update

  • name (required): string

    • Name to update

  • add_patterns: any

    • Patterns to add (category only)

  • remove_patterns: any

    • Patterns to remove (category only)

  • add_categories: any

    • Categories to add (collection only)

  • remove_categories: any

    • Categories to remove (collection only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYesArguments for category_collection_update tool.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description bears full burden. It explains the incremental update behavior but lacks details on side effects, permissions, or error conditions. Could be more transparent.

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 with sections and bullet points. Every sentence adds value.

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 presence of an output schema and moderately complex parameters, the description adequately covers the tool's behavior and distinguishes from siblings. Could include more about constraints or expected outcomes.

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 description coverage is 100%, so baseline 3. The description restates parameter purposes in a structured way but adds minimal new meaning beyond the 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?

The description clearly states it updates categories or collections incrementally, and explicitly differentiates from the sibling tool category_collection_change for complete replacement.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use (incremental updates) and when-not-to-use (complete replacement), naming the alternative tool category_collection_change.

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

Install Server

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/deeprave/mcp-guide'

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