nc-mcp-server

list_versions

Read-onlyIdempotent

Retrieve version history for a Nextcloud file using its file ID. Get details like version ID, last modified, size, author, and label for each version.

Instructions

List versions of a file by its file ID.

Returns the version history. Use the file_id from list_directory or search_files results.

Args: file_id: The numeric Nextcloud file ID. limit: Maximum number of versions to return (1-200, default 50). offset: Number of versions to skip for pagination (default 0).

Returns: JSON with "data" (list of versions with version_id, last_modified, size, content_type, author, label) and "pagination" (count, offset, limit, has_more).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_id": "<file_id>"
    },
    "name": "list_versions"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`file_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already carry readOnlyHint=true, idempotentHint=true, and destructiveHint=false, lowering the bar. The description adds genuine value beyond those by disclosing the pagination behavior (limit/offset, has_more) and the exact return structure (version fields and pagination object). This is meaningful context on top of the safety profile.

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?

Purpose is front-loaded in the first line, followed by an efficient Args/Returns structure. Every sentence earns its place — parameter documentation, pagination semantics, and return format. No fluff or repetition of schema data.

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?

For a 3-parameter, 1-required tool with 0% schema coverage and no shown output schema, this description is complete: purpose, how to source the key input, full parameter semantics, and a detailed return/pagination contract. Nothing an agent needs to call it correctly is missing.

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 description coverage is 0%, so the description carries the full burden — and it delivers. All three parameters are documented with semantics: file_id as the numeric Nextcloud file ID, limit with its 1-200 range and default 50, and offset as pagination skip with default 0. This fully compensates for the empty schema descriptions.

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?

States a specific verb and resource: 'List versions of a file by its file ID.' This is distinct from siblings like restore_version (which restores a version) and get_file (which fetches content). The purpose is unambiguous and separates cleanly from related tools.

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?

Provides clear context on how to obtain the required parameter ('Use the file_id from list_directory or search_files results'), but never names the natural alternative sibling restore_version or states when to pick this over it. There is no explicit when-to-use versus when-not-to guidance, just a hint for sourcing the input.

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

Deploy Server