Skip to main content
Glama
ahamedfo

IBM Content Services MCP Server

by ahamedfo

download_document_content

Read-only

Downloads original document content (e.g., PDF) to a local folder without checking out the document. Provides read-only access for downstream processing of file bytes.

Instructions

Downloads a document's original content (e.g., the raw PDF file) from the content repository to a local folder WITHOUT checking the document out.

This is a read-only operation: it places NO reservation/lock on the document, so no checkin_document or cancel_document_checkout call is needed afterwards. Use this tool when the original file bytes are needed (e.g., for downstream image or PDF processing) rather than the extracted text.

: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"). :param download_folder_path: Path to the folder where the document content will be saved (required). The folder is created if it does not exist.

:returns: If successful, returns a dictionary containing: - document_id (str): The document's ID. - files (list): One entry per downloaded content element, each containing: - file_path (str): The full path of the downloaded file. - retrieval_name (str): The content element's original file name. - content_type (str): The MIME type of the content. - content_size (int): The size of the content in bytes. If unsuccessful, returns a ToolError with details about the failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYes
download_folder_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

While annotations already declare readOnlyHint=true, the description adds significant behavioral context: it confirms the operation places no reservation/lock, so no checkin or cancel is needed. It also details the return format (dictionary with document_id, files list) and failure mode (ToolError), which go beyond the annotations.

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 well-structured with a clear opening, usage context, parameter documentation using :param tags, and return documentation using :returns. It is concise but comprehensive, with no superfluous information.

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

Completeness5/5

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

Given the tool's low complexity (2 parameters, output schema present), the description is fully complete. It covers purpose, behavior, parameters, return format, and error handling. No missing details are needed for an agent to invoke it correctly.

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?

The input schema has 0% description coverage, but the description fully explains both parameters: identifier can be an ID or path, and download_folder_path is a required folder path that is created if missing. This adds critical meaning beyond the basic schema types.

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 that the tool downloads original content (e.g., raw PDF) without checking out the document, distinguishing it from sibling tools like checkout_document, checkin_document, and others. The verb 'downloads' and resource 'document content' are specific and unambiguous.

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

Usage Guidelines4/5

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

The description explicitly tells when to use this tool: when original file bytes are needed instead of extracted text. It also clarifies that no checkin or cancel checkout is needed, implying it's a read-only alternative to checkout. However, it does not explicitly state when not to use it, but the contrast with sibling tools provides indirect guidance.

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

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