Skip to main content
Glama
Sign In
mcp-paperless-ngx

mcp-paperless-ngx

by tobee89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete share link bundle

delete_share_link_bundle
Destructive

Revoke a share link bundle immediately to stop all bundled documents from being publicly accessible, leaving the documents themselves unchanged.

Instructions

Revoke a share link bundle immediately. Every document in the bundle stops being publicly reachable; the documents themselves are untouched.

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": {
      "id": "<id>"
    },
    "name": "delete_share_link_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish destructive, non-readOnly, non-idempotent behavior, and the description adds valuable specificity: revocation is immediate, it affects every document in the bundle, and the documents themselves are untouched. This clarifies exactly what is destroyed beyond what the annotations convey, and does not contradict them.

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?

Two sentences with no filler; the action and immediate effect are front-loaded, and the 'documents themselves are untouched' clause earns its place by preventing a common confusion with document deletion.

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 one-parameter destructive tool with strong annotations, the description is almost complete: it states the scope and limits of destruction clearly. The only meaningful gap is that it does not define or point to how the required id is obtained, which would make invocation fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the meaning of the id parameter beyond the tool's name. It neither states that id is the share link bundle's identifier nor says how to obtain it, so it fails to compensate for the missing schema documentation.

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?

The description uses a specific verb ('Revoke') and resource ('share link bundle'), and immediately clarifies the consequence: every document in the bundle stops being publicly reachable. This clearly differentiates it from sibling tools like delete_share_link and delete_document, which affect different objects.

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 description implies when to use it—whenever a share link bundle needs to be revoked—and states the immediate effect. However, it gives no explicit when-not-to-use guidance and does not mention alternatives such as delete_share_link for revoking a single link.

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