Skip to main content
Glama

AdsAgent — Meta Ads MCP

assets_list_businesses

List Meta Business Managers visible to this workspace. 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. Changed7 schema fields changed
    • addedOutput schema / $defs
      Added value: +{
      +  "s4": {
      +    "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"
      +  },
      +  "s7": {
      +    "properties": {
      +      "status": {
      +        "enum": [
      +          "requires_validation",
      +          "awaiting_assets",
      +          "blocked"
      +        ],
      +        "type": "string"
      +      },
      +      "summary": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "status",
      +      "summary"
      +    ],
      +    "type": "object"
      +  }
      +}
    • 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/s7"
      +}
    • 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/s7"
      +    },
      +    "observed_at": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "routing_errors": {
      +      "type": "integer"
      +    },
      +    "scope": {
      +      "enum": [
      +        "tenant",
      +        "fb_user"
      +      ],
      +      "type": "string"
      +    },
      +    "updated_assets": {
      +      "properties": {
      +        "ad_accounts": {
      +          "$ref": "#/$defs/s4"
      +        },
      +        "businesses": {
      +          "$ref": "#/$defs/s4"
      +        },
      +        "pages": {
      +          "$ref": "#/$defs/s4"
      +        }
      +      },
      +      "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.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false on a list operation, which is counterintuitive; the description resolves this by disclosing "Cache miss/authorized refresh may queue private work." That explains the non-read-only nature and is genuine value beyond the annotation flags. It does not, however, describe pagination or rate implications.

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?

Front-loaded with the purpose, which is good, but the trailing clauses read as telegraphic fragments ("filter then paginate; assets_lookup_business_links") whose meaning is left to inference. Small but not tight.

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?

An output schema exists, so return values need not be explained, but with 0% parameter coverage and a non-read-only mutation-adjacent behavior (queued private work), the description leaves the agent without enough to invoke the tool confidently.

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 coverage is 0% across 6 parameters, so the description must carry the load. "filter then paginate" loosely maps to search and cursor/limit, but refresh, fb_user_label, and connection_context are undocumented in both schema and description.

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+resource ("List Meta Business Managers") and scopes it to "visible to this workspace." It is distinguishable from siblings like assets_list_pages or assets_list_ad_accounts by resource, though it does not explicitly name a same-domain alternative to route away from.

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?

"filter then paginate" and the trailing fragment "assets_lookup_business_links" imply ordering and a related tool, but neither is framed as a when-to-use/when-not rule. No exclusions or prerequisites are stated.

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