Skip to main content
Glama

Delete share link

delete_share_link
DestructiveIdempotent

Revoke a preview share link (stops working within seconds)

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": {
      "share_id": "<share_id>"
    },
    "name": "delete_share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_idYes
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The phrase "stops working within seconds" does add genuine timing behavior not present in the structured fields, but nothing is said about what happens on an invalid or already-revoked share_id, or on permission failure.

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?

A single front-loaded clause with a parenthetical qualifier; nothing is padded or wasted. The parenthetical timing note earns its place by adding behavior the annotations do not express.

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 two-parameter destructive tool with no output schema and full annotation coverage of destructiveness and idempotency, the description is minimally sufficient. It does not address error behavior or how to obtain a share_id, which an agent deleting a link would plausibly need.

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?

The required share_id has no description in the schema and the description here says nothing about its format or where it comes from, leaving 50% schema coverage unimproved. Only project_id carries any structured documentation (including the use_project session fallback), and the description does not supplement it.

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?

"Revoke a preview share link" gives a specific verb (revoke) and a specific resource (preview share link), which an agent can separate from create_share_link and list_share_links without opening a schema. It stops short of naming siblings, but the resource is narrowly defined enough to stand alone.

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 explicit statement of when to use this versus list_share_links (to find a share_id) or create_share_link to recreate one, and no prerequisite or permission context. The use case is inferable from the name alone, so the description contributes no routing guidance.

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