AdsAgent — Meta Ads MCP

templates_update

Destructive

Update an owned saved template immediately using request.template_name and flat update fields. Use new_template_name to rename or creative_distribution to change creative allocation. With no configuration maps, one source_ad_id or source_adset_id imports a fresh snapshot. Read back by exact template_name; this does not update running ads

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes
`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.

Changed1 schema field changedOct 16, 2026
- addedOutput schema / else / else / properties / content_updated_at
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
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"
+}
```
Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```
First observedSep 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare destructiveHint true, and the description adds meaningful nuance: immediate application, rename via new_template_name, read-back by exact template_name (implying the old name is invalid after rename), and that running ads are not affected. These beyond-schema behaviors are valuable. It doesn't cover permissions or reversibility of overwrites.

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?

Three dense sentences, front-loaded with the core action, then key field behaviors, then the read-back/scope caveat. No filler.

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 needn't be explained. Given destructive mutation with nested request object and 0% schema coverage, the description covers the critical behaviors (immediacy, rename, import snapshot, no ad updates), though it omits permission needs and the fate of unspecified fields.

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?

Schema coverage is 0%, so the description must compensate and does add key semantics: which fields do what (new_template_name, creative_distribution, single-source import rule) and the mutual-exclusion constraint implied by not:required for source_ad_id/source_adset_id. Many parameters (tags, ad_params, naming, etc.) remain undescribed.

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 (Update) and resource (owned saved template) plus 'immediately', distinguishing it from templates_create/get/list/delete siblings. It does not explicitly contrast against siblings like templates_get or reverse_engineer, but the verb+resource is clear.

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 concrete conditions: use new_template_name to rename, creative_distribution to change allocation, and 'with no configuration maps, one source_ad_id/source_adset_id imports a fresh snapshot'. Also clarifies it does not update running ads, effectively delineating scope vs ad-mutating tools. Lacks explicit mention of the prepare/confirm workflow alternative used by many siblings.

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?