Core Content Services MCP Server

Official

by ibm-ecm

Overview Schema Source Related Servers Discussions Admin

Python

Remote

unfile_document

Remove a document from a folder in the content repository by providing folder and document identifiers.

Instructions

Unfile a document from a folder in the content repository. This tool interfaces with the GraphQL API to unfile document from folder with the provided ids.

:param folder_id_or_path string Yes The unique identifier or path for the folder. If not provided, an error will be returned. :param document_id string Yes The unique identifier for the document. If not provided, an error will be returned.

:returns: If successful, return the folder id. Else, return a ToolError instance that describes the error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`folder_id_or_path`	Yes
`document_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.0.4May 4, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / document_id / title
```
Removed value: -"Document Id"
```
removedInput schema / properties / folder_id_or_path / title
```
Removed value: -"Folder Id Or Path"
```

removedInput schema / title

Removed value: -"unfile_documentArguments"

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: -"unfile_documentOutput"
```
addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```

First observedv1.0.0Jan 8, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Without annotations, the description carries the transparency burden. It mentions using the GraphQL API and indicates success returns a folder ID, while failure returns a ToolError. However, it does not disclose whether the operation is destructive or requires authentication.

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 fairly concise, starting with the primary purpose and including parameter details. The docstring format is slightly lengthy but well-organized.

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?

For a simple tool with two required string parameters, the description covers purpose, parameter semantics, and return value. It is adequate for an agent to understand and invoke the tool correctly.

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?

The description includes docstring-like parameter documentation explaining that folder_id_or_path and document_id are unique identifiers and that they are required, adding meaning beyond the schema's type-only definitions.

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 tool's purpose: 'Unfile a document from a folder in the content repository.' This directly matches the name and distinguishes it from sibling tools like file_document.

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, nor does it mention prerequisites or common usage scenarios. It only describes the basic operation.

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