Skip to main content
Glama

Set a share link

websiteShareLinks_set
DestructiveIdempotent

Points a path on the website, such as /menu.pdf, at a ready image or file in its asset library. A file has one link: a new path moves it, and setting a linked path to another file moves that path (how a replaced file keeps its link). Paths used by pages, config redirects, or the site server are refused; at most 100 per website. Applies at once on every site host, without publishing, as a 302 to the file’s current delivery 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": {
      "websiteId": "<websiteId>",
      "path": "<path>",
      "assetId": "<assetId>"
    },
    "name": "websiteShareLinks_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath on the website that opens the file, such as `/menu.pdf`. Lowercase and starts with `/`.
assetIdYesId of a ready image or file in this website’s asset library.
websiteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructive, idempotent, open-world and non-read-only behavior, yet the description adds real value: what gets destroyed (a file's existing link when a new path is set), that paths used by pages, redirects or the server are refused, the 100-per-site cap, and that changes apply immediately on every host without publishing as a 302 to the current delivery URL. It does not cover auth/permissions, which is the main remaining gap.

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?

Three dense sentences with the core mapping stated first, followed by collision semantics and constraints. Front-loaded and free of filler, though the parenthetical about a replaced file keeping its link is slightly tangled.

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 three-parameter mutation with annotations covering the safety profile and no output schema, the description covers collision behavior, refusal rules, limits, propagation to all hosts, and the 302 redirect nature. Only authentication requirements and the exact response are unstated, which are minor for this complexity.

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 coverage is 67% and already documents `path` (format, example, lowercase) and `assetId` (ready image or file), so the description adds little beyond it. `websiteId` remains undocumented in both places, and the 'one link per file' rule is behavioral rather than parameter-level.

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: pointing a website path at an asset in the library, with a concrete example (`/menu.pdf`). It is clearly distinct from the sibling list/remove operations by implication of 'set', though it never names those siblings explicitly.

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 explains the overwrite/move semantics and lists refusal conditions plus the 100-link cap, which implicitly tells the agent when a call will fail. However, it never routes the agent to `websiteShareLinks_list` to inspect existing links or `websiteShareLinks_remove` to delete one, so alternative selection is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources