Skip to main content
Glama
ibm-ecm

Core Content Services MCP Server

Official
by ibm-ecm
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

delete_document_version

Destructive

Remove a specific version of a document from a content repository using its ID or path.

Instructions

Deletes a specific document version in the content repository.

:param identifier: The document id or path (required). This can be either the document's ID (GUID) or its path in the repository (e.g., "/Folder1/document.pdf").

:returns: If successful, returns the deleted Document id. If unsuccessful, returns a ToolError with details about the failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changedv1.0.4
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / identifier / title
      Removed value: -"Identifier"
    • removedInput schema / title
      Removed value: -"delete_document_versionArguments"
    • removedOutput schema / $defs
      Removed value: -{
-  "ToolError": {
-    "description": "Represents an error response from a tool execution.\n\nThis class helps the LLM understand error messages and provides suggestions\nfor potential resolutions.",
-    "properties": {
-      "isError": {
-        "const": true,
-        "default": true,
-        "description": "Indicates that an error occurred during tool execution if value is True",
-        "title": "Iserror",
-        "type": "boolean"
-      },
-      "message": {
-        "description": "Detailed error message",
-        "title": "Message",
-        "type": "string"
-      },
-      "suggestions": {
-        "description": "List of suggestions for resolving the error",
-        "items": {
-          "type": "string"
-        },
-        "title": "Suggestions",
-        "type": "array"
-      }
-    },
-    "required": [
-      "message"
-    ],
-    "title": "ToolError",
-    "type": "object"
-  }
-}
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "$ref": "#/$defs/ToolError"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "description": "Represents an error response from a tool execution.\n\nThis class helps the LLM understand error messages and provides suggestions\nfor potential resolutions.",
+    "properties": {
+      "isError": {
+        "const": true,
+        "default": true,
+        "description": "Indicates that an error occurred during tool execution if value is True",
+        "type": "boolean"
+      },
+      "message": {
+        "description": "Detailed error message",
+        "type": "string"
+      },
+      "suggestions": {
+        "description": "List of suggestions for resolving the error",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "message"
+    ],
+    "type": "object"
+  }
+]
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"delete_document_versionOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations provide destructiveHint=true. The description adds detail on return values (deleted Document id or ToolError), enhancing transparency beyond annotations. However, it does not disclose if deletion is permanent or affects version numbering.

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 concise with two main sections (param and returns) and front-loads the action. It is efficient without wasted words, though slightly long due to the param explanation.

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

Completeness3/5

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

While it covers action, parameter, and return value, it fails to specify how 'identifier' identifies the version rather than the document. This ambiguity reduces completeness for a single-parameter tool.

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?

Schema coverage is 0%, so the description must compensate. It explains that 'identifier' can be a document ID (GUID) or path with an example, adding significant 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?

The description clearly states 'Deletes a specific document version in the content repository,' using a specific verb and resource. It distinguishes the tool from siblings like 'delete_version_series' which deletes all versions.

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 when to use (deleting a specific version) but does not explicitly guide when to use versus alternatives like 'delete_version_series' or mention prerequisites. Usage context is implied, not explicit.

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/ibm-ecm/ibm-content-services-mcp-server'

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