Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Revoke Connect Link

revoke_connect_link
DestructiveIdempotent

Revoke a connect link so it stops working immediately. Use when a link is exposed or no longer needed; existing connected accounts stay connected.

Instructions

Revoke a connect link so it stops working at once. Accounts already connected through it stay connected; remove them with remove_account. Needs the accounts.manage permission, which Admin holds. Returns { success: true }.

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": {
      "token": "<token>"
    },
    "name": "revoke_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe token returned by create_connect_link
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with success: true once the link is revoked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: immediate effect on the link, the non-obvious fact that existing connections persist, the required accounts.manage permission and which role holds it, and the response shape. This is exactly the operational detail the destructiveHint annotation cannot convey.

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?

Four short sentences, each carrying distinct information: effect, side effect, alternative, permission, and return value. The most important fact (immediate revocation) is front-loaded with zero padding.

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?

For a two-parameter destructive mutation, the definition covers effect, side effects, permissions, alternative, and return value, and an output schema plus idempotent/destructive hints fill the rest. Nothing an agent needs in order to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are well documented in the schema itself, including the token's origin (create_connect_link) and workspaceId semantics. The description adds nothing about parameters, so it sits at the schema-supported baseline rather than above it.

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") plus the effect ("stops working at once"), which immediately separates it from sibling remove_account by explaining that existing connections survive.

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?

Explicitly routes the agent to remove_account for the case this tool does not cover (already-connected accounts), giving clear when-to-use-which guidance. It stops short of stating preconditions like whether the link must be active or whether an already-revoked token errors, but the routing is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools