Skip to main content
Glama

List Business Manager Assets

meta_list_business_assets
Read-onlyIdempotent

Retrieve a list of owned assets (pages, ad accounts, Instagram accounts, pixels) for a Business Manager using its ID. Filter by asset type and set result limit.

Instructions

Lists assets (pages, ad accounts, Instagram accounts, pixels) for a Business Manager.

Args:

  • business_id: Business Manager ID

  • asset_type: "owned_pages", "owned_ad_accounts", "owned_instagram_accounts", "owned_pixels"

  • limit (optional, default 25): Max results

Returns asset details including IDs, names, and type-specific metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
business_idYesBusiness Manager ID
asset_typeYesType of assets to list
limitNo
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations indicate read-only and idempotent behavior; description adds return format details and default limit, providing additional context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two-sentence description front-loaded with purpose, followed by succinct parameter list; no wasted words.

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?

Adequate for a simple listing tool but missing guidance on Business Manager context and omission of response_format parameter.

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 75%; description adds meaning for 'limit' (max results) but omits 'response_format' parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists assets (pages, ad accounts, Instagram accounts, pixels) for a Business Manager, with a specific verb and resource types.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like meta_list_pages or meta_list_ad_accounts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oliverames/meta-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server