Skip to main content
Glama

AdsAgent — Meta Ads MCP

setup_check_channel_connect

Read-only

After the user confirms authorization is finished, check once using channel=meta|google_ads|tiktok and the exact connect_id from setup_begin_channel_connect. Do not poll automatically while the link remains valid; use setup_get_status for workspace readiness

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYes
connect_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNo
retryableNo
support_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / $defs
      Added value: +{
      +  "s0": {
      +    "properties": {
      +      "count": {
      +        "type": "integer"
      +      },
      +      "has_more": {
      +        "type": "boolean"
      +      },
      +      "items": {
      +        "items": {
      +          "properties": {
      +            "id": {
      +              "type": "string"
      +            },
      +            "name": {
      +              "type": [
      +                "null",
      +                "string"
      +              ]
      +            }
      +          },
      +          "required": [
      +            "id"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "count",
      +      "items",
      +      "has_more"
      +    ],
      +    "type": "object"
      +  },
      +  "s3": {
      +    "properties": {
      +      "status": {
      +        "enum": [
      +          "requires_validation",
      +          "awaiting_assets",
      +          "blocked"
      +        ],
      +        "type": "string"
      +      },
      +      "summary": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "status",
      +      "summary"
      +    ],
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / else / properties / asset_refresh
      Added value: +{
      +  "properties": {
      +    "complete": {
      +      "type": "boolean"
      +    },
      +    "created_at": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "finished_at": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "last_refreshed_at": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "launch_readiness": {
      +      "$ref": "#/$defs/s3"
      +    },
      +    "refresh_scope": {
      +      "enum": [
      +        "tenant",
      +        "fb_user"
      +      ],
      +      "type": "string"
      +    },
      +    "refresh_summary": {
      +      "properties": {
      +        "failed_connections": {
      +          "items": {
      +            "properties": {
      +              "label": {
      +                "type": "string"
      +              },
      +              "reason": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "label",
      +              "reason"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "failed_connections_count": {
      +          "type": "integer"
      +        },
      +        "failed_connections_has_more": {
      +          "type": "boolean"
      +        },
      +        "launch_readiness": {
      +          "$ref": "#/$defs/s3"
      +        },
      +        "observed_at": {
      +          "type": [
      +            "null",
      +            "string"
      +          ]
      +        },
      +        "routing_errors": {
      +          "type": "integer"
      +        },
      +        "scope": {
      +          "enum": [
      +            "tenant",
      +            "fb_user"
      +          ],
      +          "type": "string"
      +        },
      +        "updated_assets": {
      +          "properties": {
      +            "ad_accounts": {
      +              "$ref": "#/$defs/s0"
      +            },
      +            "businesses": {
      +              "$ref": "#/$defs/s0"
      +            },
      +            "pages": {
      +              "$ref": "#/$defs/s0"
      +            }
      +          },
      +          "required": [
      +            "ad_accounts",
      +            "pages",
      +            "businesses"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "observed_at",
      +        "scope",
      +        "updated_assets",
      +        "failed_connections",
      +        "launch_readiness"
      +      ],
      +      "type": [
      +        "null",
      +        "object"
      +      ]
      +    },
      +    "requested_scope": {
      +      "enum": [
      +        "tenant",
      +        "fb_user"
      +      ],
      +      "type": "string"
      +    },
      +    "started_at": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "status": {
      +      "type": "string"
      +    },
      +    "task_ref": {
      +      "type": "string"
      +    },
      +    "task_status": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "complete"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / else / properties / ready_scope
      Added value: +{
      +  "enum": [
      +    "onboarding_only"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The readOnlyHint is reinforced by 'check once' and 'do not poll automatically'—the tool has no side effects or long-running behavior. The description adds temporal context (after authorization confirmation) and constraint (single execution) that annotations alone do not cover.

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?

Two sentences efficiently cover trigger, parameter source, and an explicit exclusion. Every clause adds actionable guidance, and the main instructions are front-loaded.

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?

The description fully covers the 2-parameter tool for the intended one-time check, leverages the output schema for return understanding, and gives clear next-step alternatives. Nothing needed for calling 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?

With 0% schema description coverage, the description must compensate. It specifies channel values (meta|google_ads|tiktok) and ties connect_id to the exact ID from setup_begin_channel_connect, which is critical for correct use. This is meaningful beyond the schema names, though it stops short of a formal enum.

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 clearly states the tool checks a channel connect using channel and connect_id, and references setup_begin_channel_connect as the source of the connect_id. It differentiates from siblings like setup_check_facebook_connect (Facebook-specific) and setup_get_status (workspace readiness) by narrowing to channel connect verification.

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?

It gives explicit guidance: call only after the user confirms authorization is finished, exactly once, and not repeatedly while the link is valid. It also redirects to setup_get_status for workspace readiness, which provides clear when-to-use and when-not-to-use context against alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources