Skip to main content
Glama

Remove (disconnect) an account

remove_channel
DestructiveIdempotent

Disconnects an account from the workspace: Shager deletes its keys for the account (and, where the network offers it, cancels Shager's access there; see get_network_features revoke). Posts already published keep their numbers; posts waiting to go out won't go to it. Only the account's owner can connect it again (create_connect_link), so this first needs a manager's OK in Shager: the call answers needs_confirmation with confirm_url; after they approve, make the same call again. To stop posting for a while without losing the connection, use set_channel_status PAUSED instead. (Not available in an unclaimed sandbox.)

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": {
      "workspace_id": "<workspace_id>",
      "channel_id": "<channel_id>"
    },
    "name": "remove_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYes
workspace_idYesWorkspace id from list_workspaces
confirmation_tokenNoThe confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true, openWorldHint=true), the description discloses exactly what is destroyed (Shager's keys), what is preserved (published posts keep their numbers), what is dropped (queued posts), who can reconnect (only the owner), and the needs_confirmation/confirm_url approval flow. That is rich behavioral context the annotations 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded and every clause carries information (destruction scope, retained posts, reconnect ownership, approval flow, alternative tool). It is dense and somewhat run-on with nested parentheticals, but no sentence is wasted.

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 destructive three-parameter tool with no output schema, the description covers consequences, side effects, permissions, the two-phase confirmation protocol, sandbox restrictions, and the safer alternative. Nothing material an agent needs to invoke it correctly appears to be 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 67 percent, and the description compensates for the least obvious parameter by explaining the confirmation_token lifecycle: the call returns needs_confirmation with a confirm_url, and the same call must be repeated after human approval. workspace_id and channel_id are left to the schema, which already labels workspace_id, so the added value is real but not exhaustive.

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?

The description opens with a specific verb and resource ('Disconnects an account from the workspace') and immediately states the concrete effect: Shager deletes its keys for the account. It also distinguishes itself from set_channel_status (pause) and create_connect_link (reconnect), so an agent can tell it apart from siblings without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit alternative for the softer case ('To stop posting for a while without losing the connection, use set_channel_status PAUSED instead') and states prerequisites: manager approval in Shager and unavailability in an unclaimed sandbox. It also spells out the two-step confirmation sequence needed before the call succeeds.

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