Skip to main content
Glama

AdsAgent — Meta Ads MCP

by md.adsagent
OverviewDiscussionsAdmin

assets_refresh_all

Queue an asset snapshot refresh

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNo
retryableNo
support_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedOutput schema / $defs
      Added value: +{
+  "s0": {
+    "properties": {
+      "count": {
+        "type": "integer"
+      },
+      "has_more": {
+        "type": "boolean"
+      },
+      "items": {
+        "items": {
+          "properties": {
+            "id": {
+              "type": "string"
+            },
+            "name": {
+              "type": [
+                "null",
+                "string"
+              ]
+            }
+          },
+          "required": [
+            "id"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "count",
+      "items",
+      "has_more"
+    ],
+    "type": "object"
+  },
+  "s3": {
+    "properties": {
+      "status": {
+        "enum": [
+          "requires_validation",
+          "awaiting_assets",
+          "blocked"
+        ],
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "status",
+      "summary"
+    ],
+    "type": "object"
+  }
+}
    • addedOutput schema / else / else / properties / created_at
      Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
    • addedOutput schema / else / else / properties / finished_at
      Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
    • addedOutput schema / else / else / properties / launch_readiness
      Added value: +{
+  "$ref": "#/$defs/s3"
+}
    • addedOutput schema / else / else / properties / refresh_summary
      Added value: +{
+  "properties": {
+    "failed_connections": {
+      "items": {
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "reason": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "reason"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "failed_connections_count": {
+      "type": "integer"
+    },
+    "failed_connections_has_more": {
+      "type": "boolean"
+    },
+    "launch_readiness": {
+      "$ref": "#/$defs/s3"
+    },
+    "observed_at": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "routing_errors": {
+      "type": "integer"
+    },
+    "scope": {
+      "enum": [
+        "tenant",
+        "fb_user"
+      ],
+      "type": "string"
+    },
+    "updated_assets": {
+      "properties": {
+        "ad_accounts": {
+          "$ref": "#/$defs/s0"
+        },
+        "businesses": {
+          "$ref": "#/$defs/s0"
+        },
+        "pages": {
+          "$ref": "#/$defs/s0"
+        }
+      },
+      "required": [
+        "ad_accounts",
+        "pages",
+        "businesses"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "observed_at",
+    "scope",
+    "updated_assets",
+    "failed_connections",
+    "launch_readiness"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}
    • addedOutput schema / else / else / properties / requested_scope
      Added value: +{
+  "enum": [
+    "tenant",
+    "fb_user"
+  ],
+  "type": "string"
+}
    • addedOutput schema / else / else / properties / started_at
      Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The description adds the queuing behavior, implying an asynchronous operation, which is not in the annotations. It does not disclose side effects, scope, or that it likely affects all assets (despite the tool name). Since annotations already mark it as non-read-only and non-destructive, the description's added value is limited to the queue hint.

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?

One sentence with no filler. It is appropriately small for a parameterless action, and the main verb is front-loaded.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless tool with an output schema, the description is minimal but leaves open what 'asset snapshot' means and what the refresh will update. It also doesn't mention how to check the queued job's status, though task-tracking siblings exist. It is adequate but not rich.

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?

The tool has zero parameters, so there are no parameter semantics to document. The description doesn't need to elaborate; the empty schema is self-sufficient and the baseline for 0 parameters is 4.

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 ('Queue') on a specific resource ('asset snapshot refresh'), which is more than a tautology. However, it doesn't clarify the scope ('all' assets) or explain what an asset snapshot is, and it doesn't distinguish itself from other refresh tools like fb_users_refresh_routing. This is clear core purpose but with some ambiguity.

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 invoke this tool versus the many asset-related siblings (e.g., assets_list_ad_accounts, assets_lookup_business_links). The description doesn't mention that it's an asynchronous bulk refresh, nor does it indicate prerequisites or follow-up steps. This leaves the agent without context for choosing it.

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