Skip to main content
Glama

AdsAgent — Meta Ads MCP

assets_list_ad_accounts

List Meta ad accounts this workspace can use, with routing flags. Cache miss/authorized refresh may queue private work; filter then paginate; assets_lookup_business_links

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
searchNo
refreshNo
fb_user_labelNo
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 / then / properties / category
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / then / properties / expected
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / then / properties / failure_kind
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / then / properties / responsibility_hint
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / then / properties / route
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / 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. Changed13 schema fields changed
    • addedOutput schema / $defs
      Added value: +{
      +  "s0": {
      +    "items": {
      +      "properties": {
      +        "id": {
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": [
      +            "null",
      +            "string"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "id"
      +      ],
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "s2": {
      +    "properties": {
      +      "count": {
      +        "type": "integer"
      +      },
      +      "has_more": {
      +        "type": "boolean"
      +      },
      +      "items": {
      +        "$ref": "#/$defs/s0"
      +      }
      +    },
      +    "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 / properties / items / items / properties / pages / $ref
      Added value: +"#/$defs/s0"
    • removedOutput schema / else / properties / items / items / properties / pages / items
      Removed value: -{
      -  "properties": {
      -    "id": {
      -      "type": "string"
      -    },
      -    "name": {
      -      "type": [
      -        "null",
      -        "string"
      -      ]
      -    }
      -  },
      -  "required": [
      -    "id"
      -  ],
      -  "type": "object"
      -}
    • removedOutput schema / else / properties / items / items / properties / pages / type
      Removed value: -"array"
    • addedOutput schema / else / properties / items / items / properties / pixels / $ref
      Added value: +"#/$defs/s0"
    • removedOutput schema / else / properties / items / items / properties / pixels / items
      Removed value: -{
      -  "properties": {
      -    "id": {
      -      "type": "string"
      -    },
      -    "name": {
      -      "type": [
      -        "null",
      -        "string"
      -      ]
      -    }
      -  },
      -  "required": [
      -    "id"
      -  ],
      -  "type": "object"
      -}
    • removedOutput schema / else / properties / items / items / properties / pixels / type
      Removed value: -"array"
    • addedOutput schema / else / properties / refresh_meta / properties / created_at
      Added value: +{
      +  "type": [
      +    "null",
      +    "string"
      +  ]
      +}
    • addedOutput schema / else / properties / refresh_meta / properties / finished_at
      Added value: +{
      +  "type": [
      +    "null",
      +    "string"
      +  ]
      +}
    • addedOutput schema / else / properties / refresh_meta / properties / launch_readiness
      Added value: +{
      +  "$ref": "#/$defs/s3"
      +}
    • addedOutput schema / else / properties / refresh_meta / 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/s2"
      +        },
      +        "businesses": {
      +          "$ref": "#/$defs/s2"
      +        },
      +        "pages": {
      +          "$ref": "#/$defs/s2"
      +        }
      +      },
      +      "required": [
      +        "ad_accounts",
      +        "pages",
      +        "businesses"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "observed_at",
      +    "scope",
      +    "updated_assets",
      +    "failed_connections",
      +    "launch_readiness"
      +  ],
      +  "type": [
      +    "null",
      +    "object"
      +  ]
      +}
    • addedOutput schema / else / properties / refresh_meta / properties / requested_scope
      Added value: +{
      +  "enum": [
      +    "tenant",
      +    "fb_user"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / else / properties / refresh_meta / properties / started_at
      Added value: +{
      +  "type": [
      +    "null",
      +    "string"
      +  ]
      +}
  4. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations declare non-read-only, non-destructive behavior. The description adds meaningful context beyond annotations: cache miss or authorized refresh may queue private work (async side-effect) and results include routing flags. No auth or rate-limit details, but the added behavioral nuance is valuable.

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 is front-loaded and the description is short, but it uses semicolon-separated fragments and ends with a dangling 'assets_lookup_business_links' that lacks a verb or clear relational context, reducing structural clarity.

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?

An output schema and annotations exist, so return values need not be described. Yet with 6 undocumented parameters and weak usage guidance, the description is not complete enough for an agent to confidently invoke it, especially regarding fb_user_label and connection_context.

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 6 parameters. The description only vaguely alludes to filtering and pagination (search/limit/cursor) and to refresh behavior; parameters like fb_user_label and connection_context are entirely unexplained, so it fails to compensate for the missing schema documentation.

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?

States a specific verb 'List', resource 'Meta ad accounts', and scope 'this workspace can use'. Mentions routing flags and references a related tool (assets_lookup_business_links), aiding differentiation, though other assets_list_* siblings are not explicitly contrasted.

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?

Provides operational guidance ('filter then paginate') and a dangling sibling reference, implying usage. However, it does not state when to use this tool versus alternatives such as assets_list_businesses or assets_search_mentions, nor any when-not conditions.

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