Skip to main content
Glama
Hermoso

Hermoso

Official

Disconnect a connected account

disconnect_connector
DestructiveIdempotent

Disconnect a third-party account from the workspace and delete its stored credentials so provider tools stop working; the provider authorization remains until removed there.

Instructions

Disconnect a third-party account from this workspace (Meta, Google Ads, Google Drive/Sheets/Docs, YouTube, TikTok, LinkedIn, X, Reddit Ads, Pinterest, Google Business, Microsoft Advertising/OneDrive, Slack, …). This always drops the stored credentials, so every tool for that provider stops working immediately and posts/campaigns already published are NOT affected. IT NEVER REVOKES THE GRANT AT THE PROVIDER: the authorisation stays in place, so the same account keeps working in any other brand it is connected to, until the user removes Hermoso in that provider's own settings. The unconfirmed call names where to do that (list_connectors carries revokesAtProvider:"local") — relay it rather than promising a revoke. RECONNECTING IS THE USER'S JOB: a sign-in account needs their browser (the provider's consent screen), so an agent cannot undo this. Name the provider to the user, then call with confirm:true. Use list_connectors for the exact provider ids.

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": {
      "provider": "<provider>"
    },
    "name": "disconnect_connector"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoon a channel with several connected accounts (TikTok, X, YouTube, Threads, Bluesky, Telegram, Pinterest): remove ONLY this account (@handle or id from list_connector_accounts) and keep the others
confirmNoREQUIRED true. Reconnecting afterwards is the user's job: a sign-in account in their browser, a paste-a-key account by entering its key again
providerYesprovider id exactly as list_connectors reports it, e.g. "meta", "google_ads", "youtube", "linkedin"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.532
    • changedInput schema / properties / confirm / description
      Previous value: -"REQUIRED true — reconnecting a sign-in account afterwards needs the user's browser; a paste-a-key account is reconnected with connect_connector"New value: +"REQUIRED true. Reconnecting afterwards is the user's job: a sign-in account in their browser, a paste-a-key account by entering its key again"
  2. Changed1 schema field changedv0.1.519
    • changedInput schema / properties / account / description
      Previous value: -"on a channel with several connected accounts (TikTok, X, YouTube, Threads, Bluesky, Telegram, Reddit, Pinterest): remove ONLY this account (@handle or id from list_connector_accounts) and keep the others"New value: +"on a channel with several connected accounts (TikTok, X, YouTube, Threads, Bluesky, Telegram, Pinterest): remove ONLY this account (@handle or id from list_connector_accounts) and keep the others"
  3. Changed1 schema field changedv0.1.243
    • changedInput schema / properties / confirm / description
      Previous value: -"REQUIRED true — reconnecting needs the user's browser"New value: +"REQUIRED true — reconnecting a sign-in account afterwards needs the user's browser; a paste-a-key account is reconnected with connect_connector"
  4. Changed1 schema field changedv0.1.189
    • addedInput schema / properties / account
      Added value: +{
      +  "description": "on a channel with several connected accounts (TikTok, X, YouTube, Threads, Bluesky, Telegram, Reddit, Pinterest): remove ONLY this account (@handle or id from list_connector_accounts) and keep the others",
      +  "type": "string"
      +}
  5. Addedv0.1.161

TDQS

A4.4/5.0
Behavior5/5

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

Although annotations already flag destructiveHint=true and idempotentHint=true, the description goes well beyond them: it states stored credentials are dropped, all tools for that provider stop working, already-published posts/campaigns are unaffected, and the provider grant is NEVER revoked so the account keeps working in other brands. It also discloses that the unconfirmed call returns revokesAtProvider:"local" and that reconnection requires the user's browser, which is exactly the recovery context an agent needs before a destructive call.

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?

The purpose is front-loaded and every sentence carries operational information (consequences, non-revocation, recovery path). Heavy ALL-CAPS emphasis and some repetition of the reconnect warning cost it a point but do not obscure the message.

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, open-world, no-output-schema tool, the definition covers everything relevant: what breaks, what survives, what is not revoked, how the user recovers, and where to obtain valid provider ids. No output schema is needed and none is missing.

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% and the schema already documents all three parameters, including the confirm:true requirement and the account-handle semantics. The description only restates the provider-id source and the confirm workflow, adding little syntax or format detail beyond the structured fields, so baseline 3 applies.

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?

Opens with a specific verb and resource ('Disconnect a third-party account from this workspace') and enumerates the provider families covered, so an agent can separate it from connect_connector, leave_connector and list_connectors at a glance. The scope (workspace-level credential removal) is stated unambiguously.

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?

Gives concrete operating guidance: 'Use list_connectors for the exact provider ids', 'Name the provider to the user, then call with confirm:true', and a warning not to promise a provider-side revoke. What it lacks is an explicit contrast with leave_connector or connect_connector ('use X instead when...'), leaving the agent to infer the boundary from the brand-vs-workspace remark.

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