Skip to main content
Glama
Nextcloud MCP Server

Nextcloud MCP Server

by stack74

Preview image of a file

nextcloud_get_preview
Read-onlyIdempotent

Get a thumbnail preview of a file as Nextcloud renders it—photos, PDF first pages, office documents, or videos—so you can inspect scans, layouts, and images without downloading the full file.

Instructions

A thumbnail image of a file as Nextcloud renders it: photos, PDFs (first page), office documents and videos, depending on the preview providers the server has enabled. Use it to look at scanned documents, layouts or pictures without downloading the full file.

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": {
      "path": "<path>"
    },
    "name": "nextcloud_get_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFile path, relative to the user's Nextcloud root, e.g. '/Documents/Offers/offer-4711.pdf'
sizeNoLongest edge in pixels (64-2048, default 1024).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds genuinely new behavior context: rendering depends on server-side preview providers, and each type renders differently (first page only for PDFs). It still does not say what happens when no provider exists for a type, nor the form of the returned image, which matters for calling code.

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?

Two tightly written sentences, front-loaded with what the tool returns before the usage hint. No redundant restatement of the title or schema.

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 two-parameter read tool with full schema coverage and rich annotations, the description covers purpose, expected inputs, type coverage, and the server-dependency caveat. The remaining gap is failure behavior and return format, also absent from an output schema, but that is a minor hole for a simple tool.

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% and both parameters are well documented there, including the 64-2048 pixel range and default. The description adds nothing about parameter meaning beyond echoing 'thumbnail', so baseline 3 applies.

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?

States a specific verb and resource (fetch a rendered thumbnail of a file) and scopes it by file type: photos, PDF first pages, office documents, videos. It implicitly separates itself from nextcloud_download_file / nextcloud_read_file with 'without downloading the full file', though it never names an alternative outright.

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 a concrete when-to-use: examining scanned documents, layouts, or pictures instead of pulling the whole file. It also flags the precondition that previews depend on which preview providers the server has enabled. It lacks an explicit when-not case (e.g. full-resolution or textual inspection).

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