Skip to main content
Glama

meta_ads_campaigns_list

Retrieve a list of Meta Ads campaigns from an account with optional status filtering. Returns campaign IDs, names, statuses, objectives, and budgets to enable campaign management or further operations.

Instructions

Lists campaigns in a Meta Ads account with optional status filtering. Returns id, name, status (ACTIVE / PAUSED / DELETED / ARCHIVED), effective_status, objective (OUTCOME_SALES / OUTCOME_LEADS / etc.), buying_type, daily_budget, and lifetime_budget per campaign. Read-only. Use this to find a campaign_id before calling campaigns.get or the pause/enable helpers. For a single campaign's full detail record use meta_ads_campaigns_get.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
status_filterNoRestrict results to campaigns with this status. Omit to return all non-DELETED statuses.
limitNoMaximum records to return in a single call. Default 50. Meta Graph API caps at 1000 per page; for larger result sets reduce limit and filter client-side on the returned fields.
Behavior4/5

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

No annotations but description declares 'Read-only' and lists return fields. No mention of pagination or rate limits, but schema covers limit parameter. Behavior is well-disclosed.

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 sentences, front-loaded with purpose, no redundant information. Efficient and clear.

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

Completeness5/5

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

No output schema but description lists return fields. No annotations but read-only stated. Tool is simple list with well-documented parameters. Complete for its complexity.

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

Parameters4/5

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

Schema has 100% coverage with clear descriptions. Description adds context about account_id fallback and status filtering behavior, slightly exceeding schema.

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?

Description clearly states it lists campaigns with optional status filtering and lists specific return fields. It distinguishes from 'get' tool for full detail.

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

Usage Guidelines5/5

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

Explicitly states to use this tool to find campaign_id before calling other tools like campaigns.get or pause/enable helpers. Also mentions alternative for full detail: meta_ads_campaigns_get.

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/logly/mureo'

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