Skip to main content
Glama
Sign In
immich-photo-manager

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete shared link

delete_shared_link
Destructive

Revoke a shared link by its UUID to make its public URL immediately inaccessible and permanently remove the link while leaving the album and photos unaffected.

Instructions

Delete (revoke) a shared link, making the public URL immediately inaccessible. The album and its photos are unaffected. Side effect: permanently removes the link.

Args:
    link_id: The shared link's UUID to delete.

Returns: JSON with deleted confirmation and link_id.

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": {
      "link_id": "<link_id>"
    },
    "name": "delete_shared_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
link_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds genuinely new information about blast radius ('the album and its photos are unaffected') and permanence ('permanently removes the link'). It stops short of saying whether the link can be recreated with the same URL or what authorization is required.

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 core effect is front-loaded in the first sentence, with safety scope and the parameter immediately after. The 'Side effect: permanently removes the link' sentence overlaps somewhat with the first sentence's 'revoke', making it marginal rather than essential.

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 annotations and an output schema, the description covers purpose, blast radius, permanence, parameter identity, and return shape. The 'Returns' sentence is largely redundant given the output schema, and permission/authorization context is missing, but nothing needed to invoke it correctly is absent.

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

Parameters4/5

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

Schema description coverage is 0%, so the burden falls on the description, which identifies link_id as the shared link's UUID – clarifying both the entity type and the identifier format. That is meaningful added semantics beyond the bare 'string' property, though it does not say where to obtain the UUID (e.g. list_shared_links).

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 pairs a specific verb (delete/revoke) with a specific resource (a shared link) and states the observable effect: the public URL becomes immediately inaccessible. This is clearly separable from siblings such as update_shared_link, get_shared_link, and delete_album 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the word 'revoke' – an agent can infer you call this to take a public link offline. It never states when to prefer this over update_shared_link (e.g. disabling vs deleting) or lists_shared_links for finding the id, and gives no prerequisites such as ownership or permission requirements.

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