Skip to main content
Glama

List shares

nextcloud_list_shares
Read-onlyIdempotent

Lists all file shares in an account, shares for a specific path, or items others shared with you, helping you audit and manage access.

Instructions

List shares: all of the account's shares, the shares on one path, or the shares other people gave the account.

GET /ocs/v2.php/apps/files_sharing/api/v1/shares

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_shares"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
subfilesNo
shared_with_meNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.0
    • addedInput schema / properties / path
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / shared_with_me
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / subfiles
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  2. First observedv2.3.4

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds nothing behavioral beyond that — the raw endpoint line (GET /ocs/v2.php/...) merely restates read-only access in URL form and gives no information on pagination, result ordering, or volume of shares returned.

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 first sentence is front-loaded and dense with useful scoping information in a single line. The trailing endpoint URL is the only questionable element — it is implementation detail that consumes a line without helping an agent decide or invoke, though it does no real harm.

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 3-parameter, all-optional read tool with full annotations and no output schema, the description covers the core invocation modes adequately. The residual gaps are the semantics of `subfiles` and any indication of the returned share fields or result size, which matter more given there is no output schema to lean on.

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 0%, so the description must carry parameter meaning, and it only partly does: "the shares on one path" maps to `path` and "shares other people gave the account" maps to `shared_with_me`. The `subfiles` boolean is entirely unexplained (whether it includes shares on nested files), and the expected format of `path` is not stated, so compensation is incomplete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("List shares") and enumerates the three scoping modes: all account shares, shares on one path, and shares shared with the account. That makes the tool's identity clear, but it never names the adjacent operations (nextcloud_get_share, nextcloud_create_share, nextcloud_delete_share, nextcloud_update_share) that an agent must choose between, so sibling differentiation is only implicit.

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?

The three listed modes hint at when each parameter combination applies (path vs. shared_with_me), which is implied usage rather than explicit guidance. There is no statement of when NOT to use this tool, no mention of how it relates to nextcloud_get_share for a single share, and no prerequisites such as authentication or required permissions.

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

Deploy Server

Other Tools