Skip to main content
Glama
hashcott

Meta Ads MCP Server

by hashcott

Get Meta Ads by Ad Account

meta_ads_get_ads_by_adaccount
Read-onlyIdempotent

Retrieve ads from a Meta ad account with filtering by status, date range, and custom fields. Paginated results for efficient data extraction.

Instructions

Retrieve all ads from a specific Meta ad account with filtering and pagination.

Args:

  • act_id (string): Ad account ID prefixed with 'act_', e.g., 'act_1234567890'

  • fields (string[]): Fields per ad. Common: id, name, account_id, adset_id, campaign_id, status, effective_status, configured_status, creative, bid_amount, bid_type, created_time, updated_time, targeting, conversion_specs, recommendations, preview_shareable_link

  • effective_status (string[]): Filter by status: ACTIVE, PAUSED, DELETED, PENDING_REVIEW, DISAPPROVED, PREAPPROVED, PENDING_BILLING_INFO, CAMPAIGN_PAUSED, ARCHIVED, ADSET_PAUSED, IN_PROCESS, WITH_ISSUES

  • filtering (object[]): Additional filter objects with field, operator, value

  • limit (number): Results per page (1-100, default: 25)

  • after / before (string): Pagination cursors

  • date_preset / time_range: Date filter

  • updated_since (number): Unix timestamp — return ads updated since this time

Returns: Object with data (ad array) and paging. Use meta_ads_fetch_pagination_url with paging.next for more results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
act_idYesAd account ID prefixed with 'act_', e.g., 'act_1234567890'
fieldsNoList of specific fields to retrieve. If omitted, default fields are returned
filteringNoList of filter objects. Each has 'field', 'operator', and 'value'. Example: [{field: 'spend', operator: 'GREATER_THAN', value: 50}]
date_presetNoPredefined relative time range. Options: today, yesterday, this_month, last_month, this_quarter, maximum, last_3d, last_7d, last_14d, last_28d, last_30d, last_90d, last_week_mon_sun, last_week_sun_sat, last_quarter, last_year, this_week_mon_today, this_week_sun_today, this_year. Default: last_30d. Ignored if time_range, time_ranges, since, or until is provided
time_rangeNoCustom time range with since/until dates in YYYY-MM-DD format
updated_sinceNoReturn ads updated since this Unix timestamp
effective_statusNoFilter by effective status. Options: ACTIVE, PAUSED, DELETED, PENDING_REVIEW, DISAPPROVED, PREAPPROVED, PENDING_BILLING_INFO, CAMPAIGN_PAUSED, ARCHIVED, ADSET_PAUSED, IN_PROCESS, WITH_ISSUES
limitNoMaximum number of results to return per page (1-100, default: 25)
afterNoCursor for the next page of results, from response.paging.cursors.after
beforeNoCursor for the previous page of results, from response.paging.cursors.before
offsetNoAlternative pagination: number of results to skip
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's job is to add beyond that. It does so by explaining that the tool returns an object with 'data' and 'paging', and explicitly instructs to use meta_ads_fetch_pagination_url for more results. This discloses pagination behavior and return structure.

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?

The description is well-organized into 'Args' and 'Returns' sections, with each parameter explained concisely. It is front-loaded with the main purpose. While slightly lengthy, every sentence adds value, making it efficient for a complex tool.

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?

Given 11 parameters, 100% schema coverage, and annotations present, the description adequately explains the return value and pagination. It does not cover error handling or rate limits, but for a read-only idempotent tool, this is acceptable. The explanation of how to fetch more pages is particularly helpful.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant meaning: examples for act_id prefix, common fields list, effective_status options, default limit of 25, and how to use pagination cursors (after/before). It also explains that date_preset is ignored if time_range is provided, and describes the return object structure.

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 starts with 'Retrieve all ads from a specific Meta ad account with filtering and pagination', clearly stating the action (retrieve), resource (ads), and scope (by ad account). This distinguishes it from sibling tools like get_ads_by_adset or get_ads_by_campaign.

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?

The description mentions filtering and pagination but does not explicitly guide when to use this tool over alternatives like get_ads_by_campaign or get_ads_by_adset. Usage context is implied but not explicit with when-not or direct comparisons.

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/hashcott/meta-ads-mcp-server'

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