Skip to main content
Glama

AdsAgent — Meta Ads MCP

by md.adsagent
OverviewDiscussionsAdmin

campaigns_recreate_from_task

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_refYes
failed_items_onlyNo
connection_contextNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNo
retryableNo
support_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / connection_context
      Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • 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"
+}
  4. Changed1 schema field changed
    • 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"
+}
  5. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description's 'Prepare' wording hints at a two-phase prepare/confirm workflow, but it does not state that confirmation is required, what state is created, or what the operation affects.

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

Conciseness2/5

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

It is short, but the first sentence is a run-on with a missing period before 'Use' ('...prior create task Use the workflow's...'), which harms readability. Brevity here reflects under-specification rather than tight editing.

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 three-parameter mutation tool with an output schema but 0% parameter description coverage, the description is far too thin. It omits what task_ref accepts, the meaning of failed_items_only, and the required connection_context format, leaving an agent unable to invoke it confidently.

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% and the description explains none of the three parameters (task_ref, failed_items_only, connection_context). Worse, it references 'link_id,' which is not a parameter in the schema at all, adding confusion rather than clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'recreate from a prior create task,' which names an action and a source, but it largely restates the tool name (campaigns_recreate_from_task) rather than clarifying what 'recreate' produces. It does not clearly distinguish this from siblings like campaigns_quick_create or copy_ad_clone_structure.

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 when-to-use guidance, no prerequisites, and no reference to the confirm step (operations_confirm_campaign_recreate) or alternative recreate paths. The only directive, 'Use the workflow's original link_id when exposed,' is a data hint, not tool-selection guidance.

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 toolsInspect
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