Skip to main content
Glama

Stop sharing post

unshare_post
DestructiveIdempotent

End a post's public link: it stops opening at once for everyone who has it, and sharing the post again makes a new link. For when the user asks to stop sharing a post or to take its link back.

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": {
      "post_id": "<post_id>"
    },
    "name": "unshare_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesthe post id

Output Schema

NameRequiredDescriptionDefault
statusYes
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 idempotentHint=true, so the safety profile is covered. The description adds real behavioral context beyond them: revocation takes effect immediately for every holder of the link, and re-sharing does not restore the old URL but mints a new one. Missing only ownership/permission requirements.

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 sentences, zero padding: the primary effect and its immediacy come first, then the re-share consequence, then the usage trigger. Every clause earns its place.

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

Completeness5/5

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

An output schema exists, the single parameter is fully documented, and annotations cover safety and idempotency. The description supplies what those structured fields cannot: the visible outcome for existing link holders and the new-link behavior on re-share.

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 100% with a single required post_id, so the schema itself carries parameter meaning. The description refers to 'a post's public link' without adding format or identifier guidance, so the baseline 3 is appropriate.

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?

The description names a specific verb and resource ('End a post's public link') and explains the mechanism: the link stops opening for everyone who has it. The detail that re-sharing creates a new link implicitly separates this from delete_post, since the post itself survives — a useful distinction, though no sibling is named outright.

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?

It gives explicit user-intent triggers ('when the user asks to stop sharing a post or to take its link back'), which is exactly the routing signal an agent needs against share_post or delete_post. It stops short of stating when not to use it (e.g. use delete_post to remove the post entirely).

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