immich-photo-manager

by drolosoft

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Create shared link

create_shared_link

Create a public URL for an album to publish a gallery for external viewing without requiring authentication.

Instructions

Create a public shared link for an album, making it accessible via URL without authentication. Use this to publish a gallery for external viewing. Side effect: creates a publicly accessible URL.

Args:
    album_id: The album UUID to share publicly.
    allow_download: Allow visitors to download original files (default true).
    show_metadata: Show EXIF data to visitors (default true).
    description: Optional human-readable description for the link.

Returns: JSON with link id, key, album_id, and the full shareable 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": {
      "album_id": "<album_id>"
    },
    "name": "create_shared_link"
  }
}

Input Schema

Name	Required	Description	Default
`album_id`	Yes
`description`	No
`show_metadata`	No
`allow_download`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the security-relevant consequence: an unauthenticated public URL is created. It also quietly signals that EXIF metadata and original downloads are exposed by default. It does not say what permissions are required, whether the link can be revoked, or whether duplicate links can be created for the same album.

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 purpose sentence, then an explicit side-effect line, then Args/Returns sections - an easy scan order for an agent. There is mild redundancy between "accessible via URL without authentication" and "creates a publicly accessible URL," though the second is framed as a warning.

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 small mutation tool with one required parameter, the definition covers purpose, the public-exposure consequence, every parameter's meaning and default, and the returned fields. Since an output schema exists, the Returns line is somewhat redundant, and permission/prerequisite information is still 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 description must carry the parameters, and it documents all four with meaningful semantics: album_id is the album UUID, allow_download exposes original files, show_metadata exposes EXIF data, and description is human-readable text. Defaults (true for both booleans) are stated, which the schema only partially conveys. It adds no format or length constraints beyond that.

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?

"Create a public shared link for an album" gives a specific verb and resource, and "accessible via URL without authentication" states the scope. It is clearly distinguishable from list_shared_links/get_shared_link/update_shared_link by implication, but it never names those siblings to remove any doubt.

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?

"Use this to publish a gallery for external viewing" is a concrete when-to-use statement tied to a real scenario. It offers no when-not-to-use guidance or alternatives (e.g., linking a single asset, or a non-public share), so an agent must infer the boundaries.

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

Deploy Server