AdsAgent — Meta Ads MCP

campaigns_recreate_from_task

Prepare recreate from a prior create task Use the workflow's original link_id when exposed.

Input Schema

Name	Required	Description	Default
`task_ref`	Yes
`failed_items_only`	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"
-}
```
Changed2 schema fields changedOct 18, 2026
- addedOutput schema / else / else / properties / approval_request / properties / confirm_tool
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / else / properties / approval_request / properties / instruction_template_id
```
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"
+}
```
Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```
Changed3 schema fields changedOct 9, 2026
- addedOutput schema / else / else / properties / approval_request / properties / summary / properties / preflight / properties / checks / items / properties / provider_error_code
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / else / else / properties / approval_request / properties / summary / properties / preflight / properties / checks / items / properties / provider_error_subcode
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / else / else / properties / approval_request / properties / summary / properties / preflight / properties / checks / items / properties / reason_code
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedOct 8, 2026

addedOutput schema / else / else / properties / approval_request / properties / summary / properties / preflight

Added value: +{
+  "properties": {
+    "ad_account_id": {
+      "type": "string"
+    },
+    "billing": {
+      "properties": {
+        "available_funds_major": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "balance_semantics": {
+          "type": "string"
+        },
+        "currency": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "low_remaining_spend_cap": {
+          "type": "boolean"
+        },
+        "note": {
+          "type": "string"
+        },
+        "reported_balance_major": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "spend_cap_remaining_major": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "checked_at": {
+      "type": "string"
+    },
+    "checks": {
+      "items": {
+        "properties": {
+          "asset_id": {
+            "type": "string"
+          },
+          "asset_type": {
+            "type": "string"
+          },
+          "message": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "type": "string"
+    },
+    "timing": {
+      "properties": {
+        "account_local_now": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "hours_left_today": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "note": {
+          "type": "string"
+        },
+        "schedule_valid": {
+          "type": "boolean"
+        },
+        "timezone_name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "utc_offset_hours": {
+          "type": "number"
+        },
+        "windows": {
+          "items": {
+            "properties": {
+              "end_time": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "hours_remaining": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "hours_until_start": {
+                "type": "number"
+              },
+              "paused": {
+                "type": "boolean"
+              },
+              "potential_delivery_hours_today": {
+                "type": "number"
+              },
+              "start_time": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "version": {
+      "type": "integer"
+    },
+    "warnings": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "version",
+    "checked_at",
+    "ad_account_id",
+    "status",
+    "checks",
+    "warnings"
+  ],
+  "type": "object"
+}

First observedSep 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already establish that this is a non-read-only, non-destructive operation. The description adds little beyond that, omitting what gets prepared, whether a confirmation step follows, what side effects occur, and what prerequisites or permissions are needed.

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?

The description is short and front-loads the main action before adding the link_id note. It is efficient, though the missing punctuation and cryptic final clause slightly reduce clarity.

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?

For a mutating prepare tool with two parameters and an existing output schema, the description is too sparse. It leaves one parameter entirely unexplained and does not clarify what the preparation produces or how it relates to the confirm campaign recreation sibling.

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%, so the description must carry parameter meaning. It only indirectly implies task_ref via 'prior create task' and never explains the failed_items_only boolean; the mention of 'original link_id' refers to a field not present in the schema, adding ambiguity.

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 states a specific action, preparing a recreation from a prior create task, which distinguishes it from ordinary campaign creation. It does not explicitly name the campaign entity or differentiate it from sibling tools like campaigns_quick_create_revise, but the core operation 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies the tool is used when recreating from an existing create task and adds a conditional instruction to use the workflow's original link_id when exposed. However, it gives no explicit when-not-to-use guidance or alternatives among the many campaign and operation 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?