Skip to main content
Glama

chroma_delete_collection

Remove a specific collection from the Chroma MCP Server by specifying its name, enabling clean data management within the Chroma embedding database.

Instructions

Delete a Chroma collection.

Args:
    collection_name: Name of the collection to delete

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_nameYes

Implementation Reference

  • The main handler function for the 'chroma_delete_collection' tool. It deletes the specified collection using the Chroma client and returns a success message or raises an exception on failure.
    async def chroma_delete_collection(collection_name: str) -> str:
        """Delete a Chroma collection.
        
        Args:
            collection_name: Name of the collection to delete
        """
        client = get_chroma_client()
        try:
            client.delete_collection(collection_name)
            return f"Successfully deleted collection {collection_name}"
        except Exception as e:
            raise Exception(f"Failed to delete collection '{collection_name}': {str(e)}") from e
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a deletion operation (implying destructive action) but doesn't specify whether deletion is permanent, requires specific permissions, affects related data, or provides confirmation feedback. For a destructive tool with zero annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is appropriately brief with two sentences: a clear purpose statement followed by parameter documentation. It's front-loaded with the main action and wastes no words, though the parameter documentation could be slightly more integrated rather than separate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive deletion tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical context like what happens after deletion (confirmation? error handling?), whether deletion cascades to documents, or what permissions are required. The description should provide more operational context for such a high-impact 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?

With 0% schema description coverage and only one parameter, the description fully documents the parameter's purpose ('Name of the collection to delete'), adding essential meaning beyond the bare schema. It clearly explains what the collection_name parameter represents in the context of this deletion operation.

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 specific action ('Delete') and target resource ('a Chroma collection'), distinguishing it from siblings like chroma_modify_collection or chroma_fork_collection. It uses precise language that immediately communicates the tool's function without ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives like chroma_modify_collection or chroma_delete_documents. The description lacks context about prerequisites (e.g., whether the collection must be empty) or consequences of deletion, offering only basic functional information.

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

Related 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/chroma-core/chroma-mcp'

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