Skip to main content
Glama

AdsAgent — Meta Ads MCP

setup_get_status

Read-only

Read readiness for user-requested ad setup or explicit connection/readiness diagnosis. For unrelated tasks, skip AdsAgent tools. For requests to reveal/export private credentials (passwords, bearer tokens, MFA codes), refuse without tools. Do not run setup to offer alternatives. Connection-health, expiry and reauthorization checks remain supported

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. Changed1 schema field changed
    • addedOutput schema / else / properties / workspace_ref
      Added value: +{
      +  "description": "Opaque workspace comparison hint; not an authorization credential.",
      +  "pattern": "^workspace_[0-9a-f]{32}$",
      +  "type": "string"
      +}
  2. Changed15 schema fields changed
    • addedOutput schema / $defs / s0 / properties / count
      Added value: +{
      +  "type": "integer"
      +}
    • removedOutput schema / $defs / s0 / properties / enabled
      Removed value: -{
      -  "type": "boolean"
      -}
    • addedOutput schema / $defs / s0 / properties / has_more
      Added value: +{
      +  "type": "boolean"
      +}
    • removedOutput schema / $defs / s0 / properties / interval_min
      Removed value: -{
      -  "type": "integer"
      -}
    • addedOutput schema / $defs / s0 / properties / items
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": [
      +          "null",
      +          "string"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "id"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / $defs / s0 / properties / last_pulled_at
      Removed value: -{
      -  "type": [
      -    "null",
      -    "string"
      -  ]
      -}
    • removedOutput schema / $defs / s0 / properties / next_pull_estimate
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / $defs / s0 / properties / staleness_seconds
      Removed value: -{
      -  "type": [
      -    "integer",
      -    "null"
      -  ]
      -}
    • changedOutput schema / $defs / s0 / required
      Previous value: -[
      -  "enabled",
      -  "interval_min",
      -  "last_pulled_at",
      -  "staleness_seconds"
      -]New value: +[
      +  "count",
      +  "items",
      +  "has_more"
      +]
    • addedOutput schema / $defs / s3
      Added value: +{
      +  "properties": {
      +    "status": {
      +      "enum": [
      +        "requires_validation",
      +        "awaiting_assets",
      +        "blocked"
      +      ],
      +      "type": "string"
      +    },
      +    "summary": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "summary"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / $defs / s5
      Added value: +{
      +  "properties": {
      +    "enabled": {
      +      "type": "boolean"
      +    },
      +    "interval_min": {
      +      "type": "integer"
      +    },
      +    "last_pulled_at": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "next_pull_estimate": {
      +      "type": "string"
      +    },
      +    "staleness_seconds": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "enabled",
      +    "interval_min",
      +    "last_pulled_at",
      +    "staleness_seconds"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / else / properties / asset_refresh
      Added value: +{
      +  "properties": {
      +    "complete": {
      +      "type": "boolean"
      +    },
      +    "created_at": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "finished_at": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "last_refreshed_at": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "launch_readiness": {
      +      "$ref": "#/$defs/s3"
      +    },
      +    "refresh_scope": {
      +      "enum": [
      +        "tenant",
      +        "fb_user"
      +      ],
      +      "type": "string"
      +    },
      +    "refresh_summary": {
      +      "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"
      +      ]
      +    },
      +    "requested_scope": {
      +      "enum": [
      +        "tenant",
      +        "fb_user"
      +      ],
      +      "type": "string"
      +    },
      +    "started_at": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "status": {
      +      "type": "string"
      +    },
      +    "task_ref": {
      +      "type": "string"
      +    },
      +    "task_status": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "complete"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / else / properties / auto_pull / properties / assets / $ref
      Previous value: -"#/$defs/s0"New value: +"#/$defs/s5"
    • changedOutput schema / else / properties / auto_pull / properties / insights / $ref
      Previous value: -"#/$defs/s0"New value: +"#/$defs/s5"
    • addedOutput schema / else / properties / onboarding_guidance / properties / asset_refresh
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safe-read profile is covered. The description adds meaningful behavioral context: it will not run setup to offer alternatives and still covers connection-health, expiry, and reauthorization checks. That extra scope disclosure earns credit but stops short of richer detail.

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 purpose statement is buried inside a long, run-on sentence that strings together purpose, exclusions, refusal policy, and a closing clause. It is compact in word count but not front-loaded or clearly structured, mixing tool selection with policy in a single breath.

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?

A zero-parameter read tool with readOnly annotations and an output schema is a low-burden case, so return values need no explanation. The remaining gap is sibling differentiation among the many setup_* and connections_* tools, which the description does not resolve, leaving the agent without enough to route reliably.

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?

There are zero parameters, so per the rubric the baseline is 4. The description adds no parameter information, but none is needed since there is nothing to document.

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 a specific action ("read readiness") and resource, but the phrasing "user-requested ad setup or explicit connection/readiness diagnosis" is convoluted and does not distinguish it from close siblings like setup_readiness_check or connections_check_intent. An agent cannot tell from this text alone which of the overlapping setup/connection tools it should choose.

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 offers implied context (readiness for ad setup, connection diagnosis) and two exclusions (skip for unrelated tasks, refuse credential-reveal requests), which is more than nothing. However, the exclusions are safety-policy instructions rather than tool-selection guidance, and no sibling alternative is named for the ambiguous cases.

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