Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Disconnect a connected account

disconnect_connector
DestructiveIdempotent

Removes a provider's stored credentials from this workspace, stopping its tools immediately. Published content stays live; reconnect requires the user's browser.

Instructions

Disconnect a third-party account from this workspace (Meta, Google Ads, Google Drive/Sheets/Docs, YouTube, TikTok, LinkedIn, X, Reddit, 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 NEEDS A BROWSER (the provider's consent screen) — an agent cannot undo this. Name the provider to the user, then call with confirm:true. Use list_connectors for the exact provider ids.

Input Schema

NameRequiredDescriptionDefault
accountNoon 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
confirmNoREQUIRED true — reconnecting a sign-in account afterwards needs the user's browser; a paste-a-key account is reconnected with connect_connector
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.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"
  2. 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"
+}
  3. Addedv0.1.161

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive/idempotent/openWorld): explains that stored credentials are dropped, that all provider tools stop working, that already-published posts/campaigns are unaffected, and critically that the provider-side grant is NOT revoked. It even discloses the unconfirmed-call behavior and what to relay to the user.

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?

Front-loaded with the purpose, with CAPS emphasis reserved for the truly critical caveats (no provider-side revoke, browser needed to reconnect). It is dense and somewhat repetitive with the schema wording, and the long parenthetical provider list adds bulk, but every sentence carries decision-relevant content.

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, irreversible-from-the-agent's-perspective tool with no output schema, the description covers the essentials: what is destroyed, what is not, provider-side side effects, cross-brand impact, and how to route the user. An agent has everything needed to call it correctly and communicate the result.

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 descriptions already carry the account/confirm/provider semantics, so the description largely restates them. It adds only light invocation context ('name the provider, then confirm:true'), which is not enough to exceed the high-coverage baseline.

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+resource ('disconnect a third-party account from this workspace') and enumerates the concrete provider scope. It is clearly distinguishable from adjacent siblings like connect_connector, leave_connector, and list_connector_accounts.

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?

Explicit when-and-how guidance: 'Name the provider to the user, then call with confirm:true', use list_connectors for exact provider ids, and use the account param to remove only one account on multi-account channels. It also flags that reconnecting needs a browser, i.e. this is not agent-reversible.

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