AdsAgent — Meta Ads MCP

tasks_get_create_detail

Read-only

Read creation copy and failures

Input Schema

TableJSON Schema

Name	Required	Description	Default
`task_ref`	No
`copy_offset`	No
`include_live`	No
`copy_generation`	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 changedSep 19, 2026

addedOutput schema / else / properties / creation_snapshot / properties / ad_copies / items / properties / submitted_copy

Added value: +{
+  "properties": {
+    "availability": {
+      "type": "string"
+    },
+    "body": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "source_ad_id": {
+      "type": "string"
+    },
+    "submitted_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed7 schema fields changedSep 17, 2026

addedInput schema / properties / copy_generation
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / copy_offset

Added value: +{
+  "default": 0,
+  "type": "integer"
+}

addedOutput schema / else / properties / creation_snapshot / properties / ad_copies

Added value: +{
+  "items": {
+    "properties": {
+      "ad_id": {
+        "type": "string"
+      },
+      "adset_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "availability": {
+        "enum": [
+          "available",
+          "partial",
+          "unavailable"
+        ]
+      },
+      "body": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "captured_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "description": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "reason": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "source": {
+        "const": "task_creation_snapshot"
+      },
+      "title": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "ad_id",
+      "source",
+      "captured_at",
+      "availability",
+      "reason",
+      "title",
+      "body",
+      "description"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / else / properties / creation_snapshot / properties / ad_copies_generation
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / else / properties / creation_snapshot / properties / ad_copies_next_offset
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```

addedOutput schema / else / properties / creation_snapshot / properties / ad_copies_next_request

Added value: +{
+  "properties": {
+    "copy_generation": {
+      "type": "string"
+    },
+    "copy_offset": {
+      "type": "integer"
+    },
+    "include_live": {
+      "const": false
+    }
+  },
+  "required": [
+    "copy_offset",
+    "copy_generation",
+    "include_live"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

addedOutput schema / else / properties / creation_snapshot / properties / ad_copies_total
```
Added value: +{
+  "type": "integer"
+}
```

First observedSep 9, 2026

TDQS

C2.4/5.0

Behavior2/5

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

The readOnlyHint and destructiveHint annotations already indicate a safe read operation, and the description agrees with them. However, the description discloses no additional behavioral context beyond that, such as whether results are paginated, how copy_offset behaves, or what 'failures' includes.

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 extremely short and contains no filler, which is concise, but it is under-specified for a tool with four undocumented parameters. It reads more like a label than an explanatory definition.

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?

Even though an output schema exists and read-only annotations are present, the description fails to provide enough input semantics or usage context for reliable invocation. An agent cannot confidently determine what task_ref means or whether include_live is required for the desired behavior.

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?

Schema description coverage is 0%, so the description carries the full burden of explaining the four parameters. It names neither task_ref, copy_offset, include_live, nor copy_generation, and does not clarify their formats, defaults, or relationships.

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 names a specific action ('Read') and a specific resource ('creation copy and failures'), which makes the core purpose understandable. It does not explicitly contrast with sibling tools like tasks_get_status or tasks_list_create_history, so it lacks sibling differentiation.

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?

No guidance is provided about when to use this tool instead of task-related siblings, what state a task must be in, or what task_ref should reference. The agent is left to infer usage entirely from the tool 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?