Skip to main content
Glama
hashcott

Meta Ads MCP Server

by hashcott

Get Meta Ad Set Activity Log

meta_ads_get_activities_by_adset
Read-onlyIdempotent

Retrieve change history for a specific Meta ad set, including budget updates, targeting changes, and status modifications, with details on who made each change and when.

Instructions

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

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

Args:

  • adset_id (string): Ad set ID, e.g., '23843211234567'

  • 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: "What changes were made to ad set 23843211234567 this month?"

  • Use when: "Show me the targeting change history for this ad set"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adset_idYesAd set ID, e.g., '23843211234567'
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 readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds significant behavioral context: default time range, pagination details, and output structure, which goes beyond the annotations.

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-structured with a clear purpose, sections for Args and Returns, and examples. It is somewhat redundant with the schema but remains organized and front-loaded with key information.

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 9 parameters, nested objects, and no output schema, the description provides thorough details on return fields, pagination, and time range handling. It also directs to a sibling tool for pagination. Lacks error handling or permission notes, but overall completes the context well.

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 description coverage is 100%, so baseline is 3. The description adds value by clarifying default time range, parameter interactions (time_range overrides since/until), and providing example values, which enhances understanding beyond the 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?

The description clearly states the tool retrieves the change history for a specific ad set, with examples. It differentiates from the sibling meta_ads_get_activities_by_adaccount by specifying the resource as an ad set, and lists the types of updates returned.

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?

The description provides explicit 'Use when' examples and mentions default behavior (one week of data). It does not explicitly state when not to use or compare to alternatives, but it gives clear context for common use cases.

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