AdsAgent — Meta Ads MCP

creatives_list_cloud

Read-only

Deprecated until 2026-11-18. Use creatives_list(library_source='cloud'); it returns the same cloud files with folder_path

Input Schema

Name	Required	Description	Default
`q`	No
`limit`	No
`parent_id`	No

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 / properties / deprecated
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / else / properties / deprecation_message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / replacement
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / sunset
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / total
```
Added value: +{
+  "type": "integer"
+}
```
Changed2 schema fields changedOct 19, 2026
- addedInput schema / properties / parent_id
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / items / items / properties / parent_id
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```
Changed11 schema fields changedOct 18, 2026
- addedOutput schema / else / properties / bind_url
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / binding_ref
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / items / items / properties / error_code
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / items / items / properties / indexed_at
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```
- addedOutput schema / else / properties / items / items / properties / modified_time
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```
- addedOutput schema / else / properties / items / items / properties / next_action
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```
- addedOutput schema / else / properties / items / items / properties / path
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```
- addedOutput schema / else / properties / items / items / properties / size_bytes
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- addedOutput schema / else / properties / items / items / properties / user_message
```
Added value: +{
+  "type": "string"
+}
```
- 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

A3.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 and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: deprecation status and behavioral equivalence to creatives_list including the folder_path difference. It does not say whether calls still succeed or error during the deprecation window.

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?

Two clauses, deprecation front-loaded, nothing wasted. The only deduction is that 'Deprecated until 2026-11-18' packs an unresolved ambiguity into an otherwise efficient sentence.

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?

An output schema exists, so return values need no explanation, and the redirect covers the main decision. But for a three-parameter tool with zero schema documentation, an agent still cannot tell what q/parent_id filter or whether the endpoint remains callable, leaving it minimally adequate.

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?

Schema description coverage is 0% for all three parameters (q, limit, parent_id), so the description carries the full burden and fails it — none of the three are mentioned or explained. The only field referenced, folder_path, is a return value of the replacement tool, not one of this tool's inputs.

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 never states the verb directly, but 'Use creatives_list(library_source='cloud'); it returns the same cloud files' makes clear this is the legacy cloud-file listing path. That equivalence, plus the deprecation marker, is enough for an agent to identify it against siblings like creatives_list_folders or creatives_cloud_status.

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?

It names the alternative explicitly and even supplies the exact invocation (creatives_list with library_source='cloud'), which is the strongest form of routing guidance. The gap is the ambiguous phrase 'Deprecated until 2026-11-18' — it does not say whether calls are rejected immediately or merely discouraged until removal.

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?