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

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description adds value beyond that by explaining that 'refresh rereads stored rows' and by explicitly ruling out syncing Meta, queueing work, and saving snapshots — a meaningful behavioral boundary for a stored-data reader. No rate limits or freshness caveats, so not a 5.

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?

Very dense and front-loaded: purpose first, then filtering/pagination, then the refresh caveat and exclusions, then the sibling pointer. Every fragment carries information, though the telegraphic style ('Filter then paginate', 'BM links: ...') trades some readability for brevity.

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 exists, so return values need not be explained, and annotations cover the safety profile. The gap is parameters: with 0% schema description coverage across 6 params, the description leaves fb_user_label and connection_context undocumented, so an agent cannot fully reason about invocation. Adequate but incomplete.

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 description coverage is 0%, so the description must carry the parameter burden. It explains 'refresh rereads stored rows' and implies search/cursor/limit via 'Filter then paginate,' but fb_user_label and especially connection_context (a patterned opaque token) are left entirely unexplained. Partial compensation for a 6-parameter schema.

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 and resource: 'Read linked Meta ad accounts and their Facebook connection labels from stored workspace routing.' The 'linked ... from stored workspace routing' qualifier helps distinguish it from assets_list_ad_accounts and accounts_get_account_detail, and it names assets_lookup_business_links as the sibling for BM links. It stops short of explicitly contrasting with the nearest sibling, keeping it at 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives operational guidance ('Filter then paginate') plus negative routing: 'this tool does not sync Meta, queue work, or save snapshots,' and points to assets_lookup_business_links for BM links. No explicit statement of when to prefer this over assets_list_ad_accounts, but the exclusions and alternative reference are real guidance.

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