Skip to main content
Glama

Revoke a client's connect link

clipember_revoke_client_connect_link
DestructiveIdempotent

Revoke a connect link so it stops working at once. Accounts the client already connected through it stay connected (disconnect them separately if needed).

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": {
      "clientId": "<clientId>",
      "linkId": "<linkId>"
    },
    "name": "clipember_revoke_client_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkIdYes
clientIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 genuinely non-obvious behavior: revocation is immediate, and it does NOT cascade to accounts already connected through the link — a side effect an agent could easily get wrong.

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, effect first, caveat second. Every clause carries information and nothing is padded.

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, idempotent mutation with no output schema, the description covers the effect and the non-cascade behavior well, but leaves the two required identifiers entirely unexplained. An agent knows what will happen but not precisely what to pass.

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?

Schema description coverage is 0% and the description never mentions clientId or linkId, so an agent gets no help distinguishing the two required UUIDs or understanding why both are needed. With two undocumented parameters, the description fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Revoke a connect link") and immediately scopes the effect: the link stops working at once, but already-connected accounts remain. That scope statement distinguishes it from sibling revocation tools like revoke_preview_link and from delete_client.

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?

Implies when to use it (to kill a link's future use) and notes that disconnecting existing accounts is a separate action, but never names the tool that does that or contrasts it with clipember_revoke_preview_link. Usage is inferable rather than explicit.

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