AdsAgent — Meta Ads MCP

creatives_list

Read-only

List owned creatives; default is the whole library. For upload/how-to help, give Creative library: choose a folder, Upload images/videos, then search by filename. Use the same AdsAgent account. No list call is needed just for instructions. For reads, trust scope, use limit<=50 and follow next_cursor with unchanged filters

Input Schema

TableJSON Schema

Name	Required	Default
`q`	No
`sort`	No	newest
`limit`	No
`scope`	No	library
`cursor`	No
`created_to`	No
`folder_name`	No
`created_from`	No
`connection_context`	No

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed1 schema field changedSep 16, 2026

addedInput schema / properties / sort

Added value: +{
+  "default": "newest",
+  "enum": [
+    "newest",
+    "oldest"
+  ],
+  "type": "string"
+}

First observedSep 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish readOnly/non-destructive/openWorld=false, and the description adds real operational context: the default scope, the limit<=50 ceiling, and the next_cursor pagination contract with 'unchanged filters'. That pagination constraint is genuinely useful behavior not captured in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The pagination guidance is front-loaded well, but the middle sentences about the Creative library link and 'Use the same AdsAgent account' are tangential how-to material that dilutes the core listing instruction. Every sentence does not earn its place.

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 needn't be described, and annotations cover the safety profile. However, with 9 parameters at 0% schema coverage, six parameters remain undocumented, leaving the definition incomplete for correct invocation.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the load. It explains scope ('trust scope', 'default is the whole library'), limit ('limit<=50'), and cursor ('follow next_cursor with unchanged filters'), but leaves q, sort, created_from, created_to, folder_name, and connection_context entirely undocumented.

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?

States a specific verb and resource ('List owned creatives') and clarifies the default scope ('the whole library'). It does not name the closely-related siblings (creatives_list_cloud, creatives_list_folders), so the agent must infer which list variant to use, but the core purpose is unambiguous.

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?

Gives an explicit when-not ('No list call is needed just for instructions') and redirects upload/how-to queries to the dashboard UI. This is solid contextual guidance, though it never contrasts this tool against its sibling list tools.

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?