AdsAgent — Meta Ads MCP

creatives_cloud_status

Read-only

List connected Google Drive cloud folders with sync progress, last sync and errors. Their files already appear in creatives_list. Connect another with creatives_cloud_bind (max 10). No remaining quota is reported; over-cap downloads return cloud_daily_egress_exceeded

Input Schema

Name	Required	Description	Default
No arguments

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

Changed3 schema fields changedOct 20, 2026

addedOutput schema / else / properties / folder_count
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / else / properties / folder_limit
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / else / properties / folders

Added value: +{
+  "items": {
+    "properties": {
+      "error_code": {
+        "type": "string"
+      },
+      "file_count": {
+        "type": "integer"
+      },
+      "folder_name": {
+        "type": [
+          "null",
+          "string"
+        ]
+      },
+      "folder_ref": {
+        "type": "string"
+      },
+      "last_synced_at": {
+        "type": [
+          "null",
+          "string"
+        ]
+      },
+      "status": {
+        "type": "string"
+      },
+      "sync": {
+        "type": "object"
+      }
+    },
+    "required": [
+      "folder_ref",
+      "status"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed7 schema fields changedOct 18, 2026
- addedOutput schema / else / properties / bind_url
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / error_code
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / exceeded_error_code
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / note
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / remaining_reported
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / else / properties / support_ref
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / user_message
```
Added value: +{
+  "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"
+}
```
AddedOct 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, and the description adds real value on top: quota is not reported here and over-cap downloads surface a specific cloud_daily_egress_exceeded error. That error condition is genuinely useful behavior an agent could not infer from annotations or schema.

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?

Four short sentences, front-loaded with the core action, then the sibling distinction, then the connect path, then the quota caveat. No filler and each sentence carries distinct information.

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?

An output schema exists, so return values need no prose, and the description still supplies the operational caveats (max 10 connections, no quota reporting, egress error) an agent needs. Nothing material is missing for a parameterless status tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for a parameterless tool applies. No parameter-level claims are made or needed.

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 and resource (list connected Google Drive cloud folders) plus what each entry carries (sync progress, last sync, errors). It also distinguishes itself from creatives_list by noting that the underlying files already show up there.

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?

Explicitly routes the agent: use creatives_cloud_bind to add another connection and consult creatives_list for the files themselves. It does not address the very similar siblings creatives_list_cloud and creatives_refresh_cloud, so the routing is clear but not exhaustive.

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?