Skip to main content
Glama
mikusnuz

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_account_activities

Retrieve an ad account's activity log to track changes made to campaigns, ad sets, and ads for auditing and troubleshooting.

Instructions

Get activity log for the ad account. Shows changes made to campaigns, ad sets, ads, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor for next page
limitNoNumber of results (default 25)
fieldsNoComma-separated fields to return
account_idNoAd account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.1
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Ad account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.",
+  "type": "string"
+}
  2. First observedv1.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; 'Get' implies a read-only operation, and the second sentence discloses the kind of events returned (changes to campaigns, ad sets, ads). It says nothing about permission requirements, retention window, or how pagination behaves beyond the schema fields, so disclosure is partial rather than rich.

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?

Two short sentences, front-loaded with the core purpose and with zero filler. The second sentence earns its place by naming the object types covered. Could be marginally tighter but is well-structured.

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?

With no output schema and no annotations, the description is the only source of behavioral context, and it stops at naming the log's subject matter. It omits return shape, whether results are chronological, and any indication of scope defaults (e.g., all activities vs. a window), which an agent would need.

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 description coverage is 100% – all four parameters (after, limit, fields, account_id) are documented in the schema, including the env-var fallback for account_id. The description adds no parameter-level meaning, so the baseline 3 is appropriate.

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

Purpose4/5

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

Clear specific verb+resource: 'Get activity log for the ad account' tells the agent exactly what it retrieves. The second sentence clarifies the log's contents (campaign/ad set/ad changes), distinguishing it conceptually from insight tools like get_account_insights. However, it does not name any sibling explicitly, so an agent must still infer the boundary.

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?

There is no when-to-use guidance, no mention of when to prefer this over get_account_insights or get_campaign, and no prerequisites stated. The only implicit cue is the phrase 'activity log,' leaving the agent to guess the appropriate context.

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

Deploy Server

Other Tools