nc-mcp-server

share_collective

Creates a public link for sharing a Nextcloud collective or a single page with its subpages, with options for read-only or editable access and password protection.

Instructions

Create a public link to a collective, or to one page and its subpages. Anyone with the link can read.

Needs share rights in the collective. Sharing a page without subpages turns it into a folder page (its file becomes /Readme.md, the page ID stays), and sharing the landing page shares the whole collective. Deleting the collective's link leaves page links in place.

Args: collective_id: The numeric collective ID. page_id: A page to share on its own (default 0 = the whole collective). editable: Let people with the link edit too (default false). This needs your edit rights and is ignored when the collective does not let regular members edit; if it fails, the link exists read-only. password: Optional password the link asks for.

Returns: JSON with the share, including its url.

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": {
      "collective_id": "<collective_id>"
    },
    "name": "share_collective"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	No
`editable`	No
`password`	No
`collective_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.9.0Oct 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare it is a non-read-only, non-idempotent, non-destructive write; the description adds substantial behavior beyond that: the permission precondition, the folder-page side effect (file becomes <title>/Readme.md, page ID retained), the landing-page cascade, the editable-flag failure fallback to read-only, and that deleting the collective link preserves page links. This is exactly the mutation context an agent needs.

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 action, then behavior, then Args/Returns. Dense but every sentence adds actionable information; only the Returns section is mildly redundant given an output schema exists.

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 4-parameter mutation tool with a public-link side effect, the description covers preconditions, defaults, side effects, edge cases, and failure modes. With an output schema present, no further return-value elaboration is needed.

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: collective_id (numeric ID), page_id (default 0 = whole collective), editable (default false, needs edit rights, ignored when members can't edit, fails to read-only), and password. Every parameter gains meaning not present in the bare schema.

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 (Create) and resource (public link to a collective / page), and immediately defines the scope distinction between collective-wide and single-page sharing. An agent can distinguish this from create_share, update_collective_share, and delete_collective_share 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?

Gives clear usage context: requires share rights in the collective, page_id=0 means the whole collective, and sharing the landing page shares everything. It does not, however, explicitly name the sibling alternatives (e.g., create_share vs. update_collective_share vs. list_collective_shares) or say when not to use it.

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

Deploy Server