AdsAgent — Meta Ads MCP

setup_check_facebook_connect

Read-only

Check Facebook auth and first sync

Input Schema

Name	Required	Description	Default
`connect_id`	Yes

Output Schema

Name	Required	Description	Default
`message`	No
`retryable`	No
`support_ref`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026
- removedInput schema / properties / connection_context
```
Removed value: -{
-  "pattern": "^mctx_v1_[0-9a-f]{64}$",
-  "type": "string"
-}
```
Changed6 schema fields changedOct 15, 2026
- 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"
+}
```
Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```

Changed3 schema fields changedSep 10, 2026

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"
+}

First observedSep 9, 2026

TDQS

B3/5.0

Behavior3/5

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

The annotations already establish that this is read-only, non-destructive, and not open-world, and an output schema exists. The description adds that it checks auth and first sync, but it does not explain polling behavior, failure modes, or what happens if auth is incomplete.

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 a single compact phrase with no wasted wording and is front-loaded with the core action. Its terseness is efficient, though it leaves important specifics unstated.

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

Completeness3/5

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

The tool is simple and has annotations plus an output schema, so the description does not need to explain return values. However, for a one-parameter check tool it still leaves the connect_id source and the intended workflow position to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole required parameter, connect_id, has 0% schema description coverage, and the description never mentions it. The agent gets no guidance on where connect_id comes from, its format, or whether it is the value returned by setup_begin_facebook_connect.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb, "Check", and names the resources "Facebook auth" and "first sync". It is fairly clear what the tool does, but it does not explicitly distinguish itself from close siblings such as setup_check_channel_connect or setup_get_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool, when not to use it, or which sibling to choose instead. The agent must infer from the name that this should follow setup_begin_facebook_connect and before readiness checks, but the description does not state that relationship.

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 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?