Skip to main content
Glama
Nextcloud MCP Server

Nextcloud MCP Server

by stack74

List folder

nextcloud_list_files
Read-onlyIdempotent

List files and subfolders in a specified Nextcloud folder to inspect names, types, sizes, modification dates, and favorite or shared status; sort, filter, and page results.

Instructions

List the files and subfolders of one folder (not recursive).

Returns name, type, size, last modified and flags (favorite, shared). Start at '/' to see the top level. To find something whose location you do not know, use nextcloud_search_files instead of walking folders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nextcloud_list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoFolder path, e.g. '/' or '/Documents/2026'. Default: the root./
sortNoSort order; 'name' lists folders first.name
typeNoOnly files, only folders, or both.all
limitNoMaximum entries to return (default 100).
offsetNoSkip this many entries, for paging.
response_formatNo'markdown' for readable output, 'json' for structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description adds real value beyond that by disclosing the non-recursive traversal cost and enumerating the returned fields (name, type, size, last modified, favorite/shared flags). It does not mention paging behavior or what happens on a nonexistent path, which are the remaining behavioral gaps.

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?

Three short sentences, zero filler, ordered from what it does to scope to routing. Nothing could be removed without losing information.

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 six-parameter read tool with no output schema, the description covers purpose, scope, return fields, and the alternative tool, which is enough to call it correctly. Minor gaps remain around paging/limits and empty-or-invalid folder behavior, though limit/offset are explained in the schema.

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?

Schema description coverage is 100% with all six parameters documented including enums and defaults, so the schema does the heavy lifting and the baseline is 3. The description's only parameter-adjacent hint, starting at '/', restates the schema default rather than adding new meaning.

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 the files and subfolders of one folder') and immediately disambiguates scope with '(not recursive)'. It also names the sibling it is not, nextcloud_search_files, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit entry point ('Start at / to see the top level') and an explicit when-not plus alternative ('To find something whose location you do not know, use nextcloud_search_files instead of walking folders'). This is the exact routing decision an agent needs.

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