Skip to main content
Glama
hashcott

Meta Ads MCP Server

by hashcott

Get Meta Ad Account Activity Log

meta_ads_get_activities_by_adaccount
Read-onlyIdempotent

Retrieve the change history for a Meta ad account to see who made changes, what was changed, and when. Filter by date range or specific fields.

Instructions

Retrieve the change history (activity log) for a Meta ad account.

Returns key updates to the account and associated ad objects, including status changes, budget updates, targeting changes, and more. By default returns one week of data.

Args:

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

  • fields (string[]): Fields to retrieve. Available: actor_id, actor_name, application_id, application_name, changed_data, date_time_in_timezone, event_time, event_type, extra_data, object_id, object_name, object_type, translated_event_type

  • limit (number): Maximum activities per page

  • after / before (string): Pagination cursors

  • time_range (object): Custom range {'since':'YYYY-MM-DD','until':'YYYY-MM-DD'}. Overrides since/until

  • since (string): Start date in YYYY-MM-DD format (ignored if time_range is set)

  • until (string): End date in YYYY-MM-DD format (ignored if time_range is set)

Returns: Object with data (activity array) and paging. Each activity record contains who made the change, what was changed, when, and the specific details.

  • actor_name (string): Name of the user who made the change

  • object_type (string): Type of object: AD, ADSET, CAMPAIGN, ACCOUNT, IMAGE, REPORT, etc.

  • translated_event_type (string): Human-readable description, e.g., 'ad created', 'campaign budget updated'

  • event_time (string): Timestamp of the event

  • changed_data (string): JSON detailing what changed

Use meta_ads_fetch_pagination_url with paging.next to retrieve additional pages.

Examples:

  • Use when: "Show me all changes made to my ad account in the last week"

  • Use when: "Who changed the budget on this account in January 2024?"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
act_idYesAd account ID prefixed with 'act_', e.g., 'act_1234567890'
fieldsNoFields to retrieve. Available: actor_id, actor_name, application_id, application_name, changed_data, date_time_in_timezone, event_time, event_type, extra_data, object_id, object_name, object_type, translated_event_type
time_rangeNoCustom time range {'since':'YYYY-MM-DD','until':'YYYY-MM-DD'}. Overrides since/until
sinceNoStart date in YYYY-MM-DD format. Ignored if time_range is set
untilNoEnd date in YYYY-MM-DD format. Ignored if time_range is set
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 readOnly and idempotent. The description adds valuable context: default time range, return fields, and pagination. No contradictions.

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?

Well-structured: purpose first, then args, returns, usage hint. Slightly verbose but maintains clarity. Front-loaded with purpose.

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?

Rich schema and annotations reduce burden. Description adds default time range, return field descriptions, and pagination hints. Missing output schema is compensated by return description. Complete for effective use.

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 100%, so baseline is 3. The description adds some extra context (e.g., time_range overrides since/until, lists available fields) but largely duplicates schema descriptions. Not significantly more informative.

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 it retrieves the change history (activity log) for a Meta ad account, with specific examples of changes (status, budget, targeting). It distinguishes from sibling tool meta_ads_get_activities_by_adset by focusing on ad account level.

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?

Provides clear context: defaults to one week of data, examples of use cases ('Show me all changes', 'Who changed the budget'), and hints for pagination. Does not explicitly exclude alternative tools, but the scope is clear.

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