nc-mcp-server

list_shares

Read-onlyIdempotent

List file and folder shares from Nextcloud, either owned by you or shared with you by others. Filter by path, include reshares or subfiles, and paginate results.

Instructions

List file/folder shares from Nextcloud.

Without arguments, returns all shares owned by the current user. With a path, returns shares for that specific file or folder. With shared_with_me, returns the shares other users gave the current user instead.

Args: path: Optional file/folder path to filter shares (e.g. "/Documents/report.pdf"). reshares: If true, include shares by other users on the same files. subfiles: If true and path is a folder, list shares of files inside it (not the folder itself). shared_with_me: If true, list the shares the current user received from others (directly, through a group, a team or a Talk conversation, or from another server). "path" is then where the item shows up in the current user's files and uid_owner/displayname_owner say who shared it; federated shares have federated: true and the other server in "remote". Shares still waiting to be accepted are not included (see list_pending_shares). Cannot be combined with reshares or subfiles. limit: Maximum number of shares to return (1-200, default 50). offset: Number of shares to skip for pagination (default 0).

Returns: JSON with "data" (list of share objects) and "pagination" (count, offset, limit, has_more). share_type values: 0=user, 1=group, 3=public link, 4=email, 6=federated, 7=team, 9=federated group, 10=talk room, 12=deck card.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No
`limit`	No
`offset`	No
`reshares`	No
`subfiles`	No
`shared_with_me`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.9.0Oct 1, 2026

addedInput schema / properties / shared_with_me

Added value: +{
+  "default": false,
+  "title": "Shared With Me",
+  "type": "boolean"
+}

First observedv0.7.0Sep 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish the safe read-only, idempotent profile, and the description goes further by disclosing the return shape, the full share_type enumeration, that pending shares are excluded, and federated-share fields. That is genuine added behavioral context 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then organized into Args and Returns blocks. It is long, but given 0% schema coverage the per-parameter detail earns its place; only the cross-reference parentheticals verge on extra.

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?

Even though an output schema exists, the description fully covers the modes, constraints, parameter behavior, pagination, and result interpretation. Nothing an agent needs to call this 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 does so: every one of the six parameters gets a plain-language meaning, defaults (limit 1-200/default 50, offset default 0), example path syntax, mode-dependent semantics for path/subfiles, and a stated mutual exclusion.

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 file/folder shares from Nextcloud') and immediately differentiates its three operating modes (no args, path, shared_with_me), which is enough to distinguish it from get_share, create_share, and list_shared_items without opening any schema.

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?

Explicitly explains when each mode applies and names an alternative for the excluded case ('Shares still waiting to be accepted are not included (see list_pending_shares)'), plus states a hard constraint ('Cannot be combined with reshares or subfiles'). It doesn't contrast against list_shared_items or get_share, so it stops just short of a 5.

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

Deploy Server