Skip to main content
Glama

AdsAgent — Meta Ads MCP

accounts_list_linked_accounts

Read-only

Read linked Meta ad accounts and their Facebook connection labels from stored workspace routing. Filter then paginate. refresh rereads stored rows; this tool does not sync Meta, queue work, or save snapshots. BM links: assets_lookup_business_links

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
searchNo
refreshNo
fb_user_labelNo

Output Schema

NameRequiredDescriptionDefault
messageNo
retryableNo
support_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / connection_context
      Removed value: -{
      -  "pattern": "^mctx_v1_[0-9a-f]{64}$",
      -  "type": "string"
      -}
  2. 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"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / connection_context
      Added value: +{
      +  "pattern": "^mctx_v1_[0-9a-f]{64}$",
      +  "type": "string"
      +}
  4. 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"
      +  ]
      +}
  5. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/closed-world, and the description adds real context beyond them: it reads stored rows rather than live Meta, 'refresh' re-reads those rows, and no work is queued or snapshot saved. That clarifies the staleness model, which is the main risk with a list 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?

Front-loaded with the purpose, then constraints, then the cross-reference; no filler sentences. It is slightly telegraphic ('Filter then paginate'), which costs a little readability but not correctness.

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

Completeness4/5

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

With an output schema present and annotations covering safety, the description supplies the missing behavioral framing (stored data, no sync) that an agent needs. Gaps are limited to per-parameter detail, mainly fb_user_label and search matching.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry parameter meaning; it only explains 'refresh' and gestures at filter/paginate. It says nothing about limit bounds, cursor semantics, what 'search' matches, or what fb_user_label filters on.

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 ('Read linked Meta ad accounts and their Facebook connection labels') and pins the source ('from stored workspace routing'), which is a real distinction. It does not distinguish itself from the closest siblings assets_list_ad_accounts or connections_list, so an agent still has to infer which list is authoritative.

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?

Explicitly excludes sync/queue/snapshot behavior and routes BM-link lookups to assets_lookup_business_links, which is useful. However, the more likely confusion (this vs assets_list_ad_accounts / assets_list_businesses / connections_list) is never addressed, so usage is only implied for the main 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