Skip to main content
Glama

Revoke a post's preview link

clipember_revoke_preview_link
DestructiveIdempotent

Stop the post group's preview link from working (the page shows not found). Decisions and comments are kept. Posts held as drafts while waiting for approval stay drafts — schedule them again if they should go out.

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": {
      "groupId": "<groupId>"
    },
    "name": "clipember_revoke_preview_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupIdYesgroupId of the post (from clipember_create_post or clipember_list_scheduled_posts) — all its networks are shared together

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds genuinely new detail: the link renders as not found, decisions and comments are preserved, and approval-held drafts remain drafts. That is exactly the consequence-level context an agent needs before a destructive call, and it does not contradict the annotations.

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?

Three short sentences, front-loaded with the action, then the visible effect, then the caveat for drafts. Nothing is padded and every clause carries information.

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 single-parameter destructive tool with no output schema, the description covers side effects and post-state well. It leaves minor gaps, such as behavior when the link is already revoked or whether an error is raised, though idempotentHint suggests a safe repeat.

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?

There is only one parameter and the schema describes it fully at 100% coverage, including its source (create_post or list_scheduled_posts) and the all-networks scope. The description adds nothing about the parameter, so the baseline of 3 applies.

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 uses a specific verb and resource: 'Stop the post group's preview link from working'. That is unambiguous and an agent can tell it is the inverse of the preview-link creation flow. It stops short of naming a sibling tool, so it does not fully earn a 5.

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?

Usage is implied rather than stated: the note about drafts and 'schedule them again if they should go out' clarifies one follow-up scenario, but there is no explicit when-to-use framing and no mention of alternatives such as cancel_scheduled_post for posts that should never publish.

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