Skip to main content
Glama
yogeshkulkarni553

Content Server

deleteOrganizationContent

Remove specific content from an organization's database by providing its content ID to manage stored information.

Instructions

Delete specific content from the organization's database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentIdYesThe ID of the content to delete

Implementation Reference

  • The handler function for the deleteOrganizationContent tool. It invokes the rag_service to delete the content by ID and returns a success message.
    def delete_organization_content(self, content_id: str) -> list[str]:
        """
        Delete specific content from the organization's database.
    
        Args:
            content_id: The ID of the content to delete (required)
    
        Returns:
            Success message
        """
        self.rag_service.delete_content(content_id, self.user_id_from_environment)
        return ["Content deleted successfully"]
  • Helper function in RagService that performs the actual HTTP DELETE request to remove the specified content from the content service.
    def delete_content(self, content_id: str, user_id: str = "invalid") -> None:
        """Delete specific content from the organization's database"""
        url = f"{self.content_service_url}/contents/{content_id}"
        headers = {'userId': user_id}
    
        try:
            response = requests.delete(url, headers=headers)
            response.raise_for_status()
        except requests.RequestException as e:
            print(f"Error deleting content: {e}")
            raise
  • mcp_server.py:73-87 (registration)
    Registration of the deleteOrganizationContent tool in the list_tools handler, defining its name, description, and input schema.
    types.Tool(
        name="deleteOrganizationContent",
        description="Delete specific content from the organization's database",
        inputSchema={
            "type": "object",
            "properties": {
                "contentId": {
                    "type": "string",
                    "description": "The ID of the content to delete"
                }
            },
            "required": ["contentId"],
            "additionalProperties": False
        }
    ),
  • Input schema for the deleteOrganizationContent tool, specifying the required contentId parameter.
    inputSchema={
        "type": "object",
        "properties": {
            "contentId": {
                "type": "string",
                "description": "The ID of the content to delete"
            }
        },
        "required": ["contentId"],
        "additionalProperties": False
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool deletes content, implying a destructive mutation, but doesn't disclose critical traits like whether deletion is permanent or reversible, required permissions, rate limits, or error handling. This is a significant gap for a destructive tool with zero annotation coverage.

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 a single, efficient sentence that directly states the tool's action. It's front-loaded with the key verb 'Delete' and avoids unnecessary words. However, it could be slightly more informative without losing conciseness, such as specifying content type.

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?

Given the tool's destructive nature, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permanence, auth needs), usage context, and return values. For a mutation tool with this complexity, the description should provide more guidance to compensate for missing structured data.

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?

The input schema has 100% description coverage, with 'contentId' clearly documented as 'The ID of the content to delete'. The description adds no additional meaning beyond this, such as format examples or sourcing guidance. With high schema coverage, the baseline is 3, as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Delete') and target ('specific content from the organization's database'), which clarifies the basic purpose. However, it doesn't specify what type of content (e.g., files, records, metadata) or distinguish it from sibling tools like 'uploadContentFileAboutOrganization' that handle content creation. The purpose is clear but lacks specificity and differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., content must exist), exclusions (e.g., cannot delete certain content types), or relationships to siblings like 'listContentNames' for identifying content to delete. Usage is implied by the action but without explicit context.

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/yogeshkulkarni553/rag-mcp-py'

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