Skip to main content
Glama

Remove a share link

websiteShareLinks_remove
DestructiveIdempotent

Removes the file’s share link, if it has one. The path stops opening the file immediately on every site host.

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>",
      "assetId": "<assetId>"
    },
    "name": "websiteShareLinks_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYesId of the file whose link to remove.
websiteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructive=true, readOnly=false, idempotent=true, and openWorld=true. The description adds genuinely new context: the effect is immediate and applies across every site host, and the optional 'if it has one' clause signals a safe no-op when no link exists. It does not mention permission requirements or error behavior, so it stops short of full transparency.

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 short sentences, front-loaded with the action and followed by the effect. Nothing is repeated and nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema, the description covers the outcome well but leaves gaps: it doesn't state the response, whether the operation requires specific permissions, or what distinguishes websiteId from assetId. The annotations carry the safety profile, so the remaining omissions are moderate rather than critical.

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 50%: assetId is documented in the schema, websiteId is not described anywhere. The phrase 'the file's share link' reinforces assetId, and 'on every site host' faintly implies the websiteId scope, but the description never explains what websiteId means or how the two parameters interact.

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: removing a file's share link. It's clear what object is affected and what happens to it. It doesn't explicitly differentiate from websiteShareLinks_set, but the verb/resource pairing is unambiguous on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this versus websiteShareLinks_set (to change a link) or websiteShareLinks_list (to inspect one). The 'if it has one' clause hints at a no-op case but is behavioral rather than a usage rule, and no exclusions or prerequisites are given.

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