Meta Ads by Get MCP Ads

meta get ad activity

meta_get_ad_activity

Read-onlyIdempotent

Retrieve ad account activity logs with object, event, actor, timestamp, and extra data fields; filter by time range and paginate results to audit account changes.

Instructions

Read ad account activity logs from /{ad_account_id}/activities with object, event, actor, timestamp, and extra_data fields.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`since`	No	Optional start time accepted by Graph API, usually YYYY-MM-DD or Unix seconds.
`until`	No	Optional end time accepted by Graph API, usually YYYY-MM-DD or Unix seconds.
`cursor`	No	Pagination cursor from previous response
`adAccountId`	Yes	Ad account ID (e.g., act_123456789)

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds the endpoint path and lists the returned fields, which is useful context beyond annotations, though the field list is partially redundant with the output schema.

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?

The description is a single, front-loaded sentence that states the action, endpoint, and key return fields with zero wasted words. It is appropriately sized for a simple read 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 that the tool has rich annotations, full schema description coverage, and an output schema, the description is complete enough for an agent to call it correctly. It only lacks minor details such as pagination behavior, which is already covered by the schema's limit/cursor descriptions.

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%, so every parameter (adAccountId, limit, since, until, cursor) is already documented in the schema. The description adds no additional meaning about parameter formats, defaults, or interactions beyond what the schema provides, so the baseline of 3 applies.

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 names a specific verb (Read), a specific resource (ad account activity logs), and the exact endpoint path (/{ad_account_id}/activities), along with the fields returned. This clearly distinguishes it from all sibling tools, none of which deal with activity logs.

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 implies usage by stating that it reads activity logs, but it does not explicitly say when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The context is clear enough that an agent can infer this is for audit/activity purposes.

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

Deploy Server