Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Disconnect a connected account

disconnect_connector
DestructiveIdempotent

Disconnect a third-party account from this workspace, dropping stored credentials and disabling all tools for that provider. Published posts remain unaffected.

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. WHETHER IT ALSO REVOKES THE GRANT AT THE PROVIDER DEPENDS ON THE PROVIDER — a few (Threads, Microsoft) publish no revocation endpoint, so the authorisation stays in place until the user removes it in that provider's own settings. The unconfirmed call reports which it is for this provider (list_connectors also carries it as revokesAtProvider) — relay that verbatim 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

TableJSON 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 (destructiveHint/idempotentHint/openWorldHint) by disclosing the concrete consequences: stored credentials are always dropped, every provider tool stops working immediately, already-published posts/campaigns are unaffected, and revoke-at-provider behaviour varies by provider (Threads, Microsoft lack revocation endpoints). It also warns that reconnecting requires the user's browser and that the unconfirmed call reports revoke status.

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-loads the core action and its main consequence before the provider-specific caveats, and every sentence carries information. It is dense and the all-caps emphasis plus the duplicated browser-warning (also present in the confirm param schema) make it slightly noisier than necessary.

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, no-output-schema tool, the description covers everything needed: scope, irreversible credential loss, provider-dependent revocation, the confirm requirement, and how to enumerate valid provider ids. Nothing essential to correct invocation 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 description coverage is already 100%, so the baseline is 3. The description nonetheless adds usable meaning: why confirm must be true (browser-based reconnection) and that account removes ONLY one handle while keeping others, plus pointing to list_connectors for valid provider ids.

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 — 'Disconnect a third-party account from this workspace' — and enumerates the affected providers (Meta, Google Ads, YouTube, Slack, ...). An agent can immediately distinguish this from connect_connector and from rendering/posting tools.

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 a concrete workflow: 'Name the provider to the user, then call with confirm:true. Use list_connectors for the exact provider ids,' and explains that the account param narrows removal on multi-account channels. It does not, however, mention when NOT to use it, e.g. versus the sibling leave_connector, so the alternative-selection guidance is incomplete.

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