Metadata MCP Connector

Disconnect Channel

disconnect_channel

Destructive

Disconnect a specific advertising channel from the Metadata platform.

                USAGE INSTRUCTIONS FOR LLM:
                Use this tool to disconnect/remove integration connections for advertising channels.
                This is useful when users need to remove a channel integration or reconnect with different credentials.

                WHEN TO USE THIS TOOL:
                - User asks to "disconnect [channel name]"
                - User wants to "remove [channel] integration"
                - User needs to "unlink [channel] account"
                - User wants to "revoke [channel] access"
                - User asks to "disconnect my Facebook/LinkedIn/Twitter/Reddit/Google account"
                - User needs to "reset [channel] connection"
                - Preparing to reconnect a channel with different credentials

                SUPPORTED CHANNELS:
                - facebook: Disconnect Facebook advertising account
                - instagram: Disconnect Instagram advertising account
                - linkedin: Disconnect LinkedIn advertising account
                - twitter: Disconnect Twitter/X advertising account
                - reddit: Disconnect Reddit advertising account
                - google: Disconnect Google Ads account

                IMPORTANT NOTES:
                - This action will disconnect the channel immediately
                - Any active campaigns on this channel may be affected
                - The user will need to reconnect the channel to resume advertising
                - Always confirm with the user before disconnecting a channel
                - Check integration status first using get_integrations_status to verify the channel is connected

                COMMON SCENARIOS:

                Scenario 1 - Disconnect single channel: "Disconnect my LinkedIn account"
                → Call disconnect_channel with channel="linkedin"

                Scenario 2 - Reconnect workflow: "I want to reconnect Facebook with a different account"
                → First call disconnect_channel with channel="facebook", then guide user to reconnect

                Scenario 3 - Remove access: "Remove Google Ads integration"
                → Call disconnect_channel with channel="google"

                RESPONSE FORMAT:
                Returns a success/failure status indicating whether the channel was disconnected successfully.

                EXAMPLE: "Disconnect Facebook" → disconnect_channel(channel="facebook")

Input Schema

TableJSON Schema

Name	Required	Description	Default
`channel`	Yes	The channel to disconnect. Must be one of: reddit, facebook, linkedin, twitter, google, instagram

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses immediate disconnection, potential impact on active campaigns, and the need to reconnect. This gives the agent practical knowledge about consequences.

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 description is longer than average but well-structured with clear sections and front-loaded purpose. The scenarios section is somewhat repetitive against the usage examples, but the organization keeps it scannable and each section adds value.

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 single-parameter tool with a closed enum, the description fully covers the action, prerequisites, consequences, and expected response format ('success/failure status'). No output schema is needed for this level of simplicity.

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 already has 100% coverage with an enum and description. The tool description adds supplementary meaning by mapping each channel value to its corresponding advertising account (e.g., facebook -> Facebook advertising account). This exceeds the baseline while not being strictly necessary.

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 states a specific verb and resource: 'Disconnect a specific advertising channel from the Metadata platform.' It clearly differentiates from siblings like connect_channel by focusing on disconnection/removal of integrations.

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?

Provides explicit when-to-use guidance with concrete user phrasings ('disconnect [channel name]', 'remove [channel] integration'), lists supported channels, and recommends checking integration status via get_integrations_status before acting. Also advises confirming with the user, which is strong situational guidance.

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

All Metadata MCP Connector tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?