Skip to main content
Glama
Sign In

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channel": "<channel>",
      "connect_id": "<connect_id>"
    },
    "name": "setup_check_channel_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYes
connect_idYes

Output Schema

NameRequiredDescriptionDefault
messageNo
retryableNo
support_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / connection_context
      Removed value: -{
-  "pattern": "^mctx_v1_[0-9a-f]{64}$",
-  "type": "string"
-}
  2. 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"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / connection_context
      Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
  4. 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"
+}
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: this is a one-shot post-auth verification, not a polling endpoint, and it must be paired with setup_begin_channel_connect. It does not say what a failed or pending check implies, which keeps it below a 5.

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 dense sentences, front-loaded with the trigger condition and immediately followed by the anti-pattern and the routing alternative. No filler and no repetition of what annotations or the schema already state.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. Combined with the parameter and sequencing guidance, an agent has enough to invoke this correctly; only the meaning of a negative/unconfirmed result is unspecified.

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 0% and the schema has no enums, so the description carries the full parameter burden. It supplies the missing channel enum ('meta|google_ads|tiktok') and tells the agent the connect_id must be the exact value from setup_begin_channel_connect, which prevents stale or guessed IDs. A brief note on format validation would be needed for a 5.

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 (check) on a specific resource (channel connect), and scopes it to a single invocation after user-confirmed authorization. It implicitly separates itself from setup_check_facebook_connect via the channel parameter and from setup_begin_channel_connect by referencing it as the source of connect_id.

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?

Explicit trigger condition ('After the user confirms authorization is finished'), explicit frequency ('check once'), explicit exclusion ('Do not poll automatically while the link remains valid'), and an explicit alternative for a different need ('use setup_get_status for workspace readiness'). Nothing is left to inference.

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