Wiro MCP Server

Official

by wiroai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Disconnect an agent integration

disconnect_agent_oauth

DestructiveIdempotent

Disconnect a sign-in based integration from a deployed agent. Preview what will be removed first, then confirm to revoke access; scheduled tasks stop and the agent restarts.

Instructions

Disconnect a sign-in based integration (for example Google Ads, Meta Ads or HubSpot) from a deployed agent. Call it without confirm first: it shows what is connected and what will be removed, and changes nothing. After the user agrees, call again with confirm: true. The saved sign-in, the selected accounts and the connection's settings are cleared (your own app keys are kept), the provider is asked to revoke the access where it supports that, scheduled tasks that need the integration stop running, and a running agent restarts. It cannot be undone; reconnect with connect_agent_oauth. For plain credentials such as Telegram, clear fields with set_agent_credentials instead.

Input Schema

Name	Required	Description
`confirm`	No	false (default) only shows what would be removed. true disconnects.
`agent_guid`	Yes	The deployed agent's guid, from list_my_agents.
`credential`	Yes	The integration's credential key, for example "google-ads" or "meta-ads".

Output Schema

Name	Required	Description	Default
`title`	Yes
`message`	Yes
`accounts`	Yes
`agentGuid`	Yes
`willClear`	Yes
`credential`	Yes
`nextAction`	No
`disconnected`	Yes
`connectedBefore`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.4.1Nov 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses the two-phase dry-run behavior, exactly what is cleared, that app keys are kept, that the provider revokes access where supported, that scheduled tasks stop and the agent restarts, and that it is irreversible. This is the substantive context a destructive tool needs.

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?

The two-step instruction is front-loaded, and each sentence carries distinct information: preview behavior, consequence list, irreversibility, and alternative routing. No filler.

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?

An output schema exists so return values need not be explained, and the description covers preview semantics, side effects, and recovery path. Nothing an agent needs to invoke it correctly 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 already documents all three parameters, so the baseline is 3. The description adds real value by explaining the confirm parameter's two-step usage pattern and the semantics of credential as an integration key, though it adds little to agent_guid beyond the schema.

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 sign-in based integration from a deployed agent) and names concrete examples (Google Ads, Meta Ads, HubSpot). It is clearly distinguishable from connect_agent_oauth and set_agent_credentials.

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?

Explicitly prescribes the workflow: call without confirm first to preview, then call again with confirm:true after user agreement. It also names the alternatives for other cases (reconnect via connect_agent_oauth, plain credentials via set_agent_credentials).

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