Skip to main content
Glama

AdsAgent — Meta Ads MCP

assets_refresh_all

Queue an asset snapshot refresh

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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. 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"
      +  ]
      +}
  4. First observed

TDQS

C2.7/5.0
Behavior3/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 word "Queue" usefully signals asynchronous, fire-and-forget behavior that the annotations do not convey, but the description omits cost, throttling, scope of the refresh, and how to observe completion — real gaps for a mutation tool.

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?

A single front-loaded sentence with no filler — nothing redundant is present. The terseness is under-specification rather than bloat, so it scores well for structure while leaving content gaps.

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?

The output schema removes the need to document return values, and annotations cover safety. However, for a write operation that refreshes assets in bulk, the description omits what gets refreshed, whether the action affects every linked account, and any async/status-checking context — leaving the agent unable to reason about consequences or follow-up steps.

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% for the single connection_context parameter, and the description supplies no meaning for it at all. Since coverage is well under 50%, the description was expected to compensate and does not; only the opaque pattern in the schema hints at its nature.

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?

"Queue an asset snapshot refresh" names a verb (queue/refresh) and a resource (asset snapshot), so the operation is identifiable. But it never clarifies the scope implied by "all" in the name, nor distinguishes it from the sibling assets_refresh_ad_account, so an agent cannot tell the two apart from the text alone.

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 statement of prerequisites, and no routing to alternatives. The sibling assets_refresh_ad_account exists as an obvious narrower variant, and the description says nothing about when to prefer one over the other.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources