Skip to main content
Glama

AdsAgent — Meta Ads MCP

by md.adsagent
OverviewDiscussionsAdmin

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
connection_contextNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNo
retryableNo
support_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedOutput schema / then / properties / category
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / expected
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / then / properties / failure_kind
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / responsibility_hint
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / route
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / user_visible
      Added value: +{
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / connection_context
      Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
  3. 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"
+}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description usefully adds the 'check once, don't poll' behavioral constraint and the channel value set. It does not describe what the check returns, but an output schema exists to carry that, so this is a strong addition beyond structured fields.

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 tightly written sentences that lead with the trigger condition, then the anti-pattern and the alternative. No filler, everything front-loaded.

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?

For a read-only single-check tool with annotations and an output schema, this covers purpose, timing, alternatives, and most parameters. The only gap is the undocumented optional connection_context, which is minor.

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?

Schema description coverage is 0%, so the description must compensate. It does document channel (meta|google_ads|tiktok) and constrains connect_id to the 'exact' value from setup_begin_channel_connect, but the optional connection_context parameter (with its mctx_v1_ pattern) is never mentioned. Partial compensation for the coverage gap.

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 (check) and resource (channel connect) with an explicit trigger condition ('after the user confirms authorization is finished'). It clearly distinguishes itself from setup_get_status by naming that sibling for workspace readiness, and the channel enumeration makes its scope unambiguous.

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?

Gives explicit when-to-use ('after the user confirms authorization is finished') and when-not ('do not poll automatically while the link remains valid'), and routes to setup_get_status for workspace readiness. Both a condition and an alternative are named.

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

All AdsAgent — Meta Ads MCP toolsInspect
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