AdsAgent — Meta Ads MCP

templates_list

Read-only

List saved templates

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`search`	No
`created_after`	No
`created_before`	No
`connection_context`	No
`content_updated_after`	No
`content_updated_before`	No

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 16, 2026
- addedInput schema / properties / content_updated_after
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / content_updated_before
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / created_after
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / created_before
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / properties / items / items / properties / content_updated_at
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
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 changedOct 8, 2026

addedOutput schema / else / properties / meta / properties / metric_completeness

Added value: +{
+  "additionalProperties": {
+    "properties": {
+      "complete": {
+        "type": "boolean"
+      },
+      "excluded_rows": {
+        "type": "integer"
+      },
+      "reason": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 10, 2026
- addedOutput schema / else / properties / meta / properties / data_freshness / properties / last_pull_scope
```
Added value: +{
+  "const": "workspace"
+}
```
First observedSep 9, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no mention of pagination, filtering scope, or result ordering — so it contributes no behavioral context of its own.

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 description is only three words, so there is no padding or wasted sentence. But it is under-specified rather than genuinely concise, leaving no room for any of the necessary detail an 8-parameter tool requires.

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

Completeness2/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. Still, with 8 undocumented filter/pagination parameters and no usage guidance, the definition is not complete enough for an agent to invoke the tool correctly.

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

Parameters1/5

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

All 8 parameters (limit, cursor, search, created_after/before, connection_context, content_updated_after/before) have 0% schema description coverage, and the description supplies no meaning for any of them. With this many undocumented parameters and no compensating text, the definition fails to convey parameter semantics.

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 phrase 'List saved templates' gives a clear verb (List) and resource (saved templates), so an agent can tell the basic operation. However, it offers no differentiation from siblings like templates_get, templates_create, templates_delete, or templates_reverse_engineer.

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 guidance on when to use this tool versus the other templates_* siblings, nor any note about pagination or filtering workflow. The agent is left to infer usage entirely from the name.

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?