AdsAgent — Meta Ads MCP

creatives_refresh_cloud

Queue a background refresh of this tenant's connected cloud (Drive) folders

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

Changed5 schema fields changedOct 20, 2026

addedOutput schema / else / else / properties / deprecated
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / else / else / properties / deprecation_message
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / else / 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"
+}

addedOutput schema / else / else / properties / replacement
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / else / else / properties / sunset
```
Added value: +{
+  "type": "string"
+}
```

Changed6 schema fields changedOct 15, 2026
- addedOutput schema / else / then / properties / category
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / then / properties / expected
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / else / then / properties / failure_kind
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / then / properties / responsibility_hint
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / then / properties / route
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / then / properties / user_visible
```
Added value: +{
+  "type": "boolean"
+}
```
AddedOct 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already tell the agent this is a non-read-only, non-destructive operation, so the bar is lower. The description meaningfully adds that the work happens in the background (async, queued) rather than inline, but says nothing about what state changes on connected Drive folders, whether it can be run repeatedly, or how completion is observed.

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?

One sentence, front-loaded with the verb and scope, with zero filler. Nothing is wasted or buried.

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 the zero-parameter surface is fully covered. Only the missing pointer to the status-checking sibling and the repeated-invocation behavior keep this from being complete.

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 no parameters, so the baseline is 4; there are no argument semantics for the description to compensate for.

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?

Specific verb+resource: 'Queue a background refresh of this tenant's connected cloud (Drive) folders' — an agent knows exactly what is being refreshed and that it is queued rather than synchronous. It does not, however, differentiate itself from the near-identically named siblings creatives_cloud_refresh and creatives_cloud_status, which is the main ambiguity here.

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?

No when-to-use, when-not-to-use, or alternative is named. With both creatives_cloud_refresh and creatives_cloud_status in the sibling list, the description should say how this differs and where to check the resulting job, but it offers no routing guidance.

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?