Metadata MCP Connector

Connect Channel

connect_channel

Get the OAuth redirect URL to connect a specific advertising channel to the Metadata platform.

                USAGE INSTRUCTIONS FOR LLM:
                Use this tool to obtain the authorization URL that users need to visit to connect their advertising channel accounts.
                This tool returns a redirect URL that initiates the OAuth flow for the selected channel.

                WHEN TO USE THIS TOOL:
                - User asks to "connect [channel name]"
                - User wants to "add [channel] integration"
                - User needs to "link [channel] account"
                - User wants to "authorize [channel] access"
                - User asks "how do I connect my Facebook/LinkedIn/Twitter/Reddit/Google account?"
                - User needs to "set up [channel] connection"
                - After disconnecting a channel and wanting to reconnect
                - User asks "give me the link to connect [channel]"

                SUPPORTED CHANNELS:
                - linkedin: Connect LinkedIn advertising account
                - meta: Connect Facebook/Instagram advertising accounts (Meta Business Suite)
                - google: Connect Google Ads account
                - reddit: Connect Reddit advertising account
                - x: Connect X (Twitter) advertising account

                IMPORTANT WORKFLOW - MUST FOLLOW THESE STEPS:
                1. Call this tool to get the OAuth redirect URL
                2. Display the URL to the user clearly and instruct them to open it in their browser
                3. Explain that they need to complete the authorization process on the channel's website
                4. IMPORTANT: Ask the user to return to the chat and confirm when they have completed the connection
                5. WAIT for the user's confirmation before proceeding with any other tasks
                6. Once the user confirms the connection is complete, acknowledge it and continue

                REQUIRED USER INTERACTION:
                - The user MUST visit the returned URL in their browser to complete OAuth authorization
                - The URL will redirect to the channel's authorization page
                - After authorization, the user will be redirected back to Metadata platform
                - The connection will be active once the OAuth flow is completed successfully
                - YOU MUST WAIT for user confirmation before proceeding

                COMMON SCENARIOS:

                Scenario 1 - Connect new channel: "I want to connect my LinkedIn account"
                → Call connect_channel with channel="linkedin"
                → Show URL to user: "Please open this URL to connect your LinkedIn account: [URL]"
                → "After completing the authorization, please return here and let me know it's done so we can proceed."
                → WAIT for user confirmation

                Scenario 2 - Reconnect after disconnect: "Get me the link to reconnect Facebook"
                → Call connect_channel with channel="meta"
                → Show URL to user with instructions
                → WAIT for user confirmation

                Scenario 3 - Setup new integration: "How do I add Google Ads?"
                → Call connect_channel with channel="google"
                → Explain OAuth process and provide URL
                → Ask user to confirm when complete
                → WAIT for user confirmation

                Scenario 4 - Add Twitter/X: "Connect my X account"
                → Call connect_channel with channel="x"
                → Provide the URL to user
                → WAIT for user confirmation

                RESPONSE FORMAT:
                Returns an object containing the redirect URL for OAuth authorization.
                Example: {"redirectUrl": "https://oauth.channel.com/authorize?client_id=..."}

                EXAMPLE: "Connect LinkedIn" → connect_channel(channel="linkedin")

Input Schema

TableJSON Schema

Name	Required	Description	Default
`channel`	Yes	The channel to connect. Must be one of: linkedin, meta (for Facebook/Instagram), google, reddit, x (for Twitter)
`acknowledge_data_access`	No	Set true to confirm the person you are acting for asked to connect this channel. The response is an OAuth authorization URL that starts a credential grant into their Metadata account. Without this the call is refused.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description goes well beyond the minimal annotations by explaining that the tool only returns a redirect URL, that the user must complete OAuth in a browser, and that the connection is active only after the OAuth flow finishes. It also stresses the agent must wait for user confirmation, which is a critical behavioral constraint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with a clear summary and is well-organized with headers. However, the four 'COMMON SCENARIOS' repeat nearly identical instructions, and the workflow/user-interaction sections overlap, making it longer than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is thorough for a two-parameter tool: it explains the return format with an example, required user interaction, and the step-by-step workflow. The main gap is that the example omits the acknowledge_data_access parameter even though the schema says the call is refused without it, but this is covered in the schema.

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?

The input schema already covers both parameters with 100% descriptions and an enum for channel, so the baseline applies. The description adds a 'SUPPORTED CHANNELS' list and examples, but these largely mirror the schema's enum and don't introduce new semantics for either parameter.

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 opening sentence states a specific verb ('Get'), resource ('OAuth redirect URL'), and scope ('connect a specific advertising channel to the Metadata platform'). The description also clarifies it is the authorization-URL step, which distinguishes it from broader operations like connect_crm or disconnect_channel.

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?

A dedicated 'WHEN TO USE THIS TOOL' section lists concrete user intents ('connect [channel]', 'link [channel] account', etc.) and even covers reconnection after disconnect. However, it does not explicitly state when not to use the tool or mention alternative sibling tools, so it falls short of fully explicit routing.

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?