Skip to main content
Glama
Sign In
get-mcp-ads

Meta Ads by Get MCP Ads

by get-mcp-ads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

meta get creatives

meta_get_creatives
Read-onlyIdempotent

Retrieve ad creative content—text, images, videos, links, and calls-to-action—for specified Meta ads. Use it to inspect creative details by ad account and optional ad IDs.

Instructions

Get ad creative content: text, images, videos, links, call-to-action. Returns creative details for specified ads.

Input Schema

NameRequiredDescriptionDefault
adIdsNoSpecific ad IDs to get creatives for
limitNoMaximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
adAccountIdYesAd account ID (e.g., act_123456789)

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal 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.

  1. Changed2 schema fields changedv2.1.1
    • 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"
+  }
+]
  2. First observedv2.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds the shape of returned content (creative asset types), but says nothing about pagination behavior, rate limits, or what happens when adIds is omitted (the required adAccountId fallback).

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 verb and returned content types, with zero filler. It is efficient, though the trailing sentence ("Returns creative details for specified ads") partially restates the first.

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?

An output schema exists, so return values needn't be spelled out, and annotations carry the safety semantics. What remains missing for a crowded 40-sibling namespace is sibling disambiguation and a note on the adIds-optional listing behavior, which the description does not supply.

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 adIds, limit, and adAccountId are all documented in the schema itself, establishing a baseline of 3. The description adds no meaning beyond the schema — notably it never explains the behavior when adIds is empty, which is the one semantic gap the schema leaves open.

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?

Uses a specific verb+resource ("Get ad creative content") and enumerates the fields returned (text, images, videos, links, CTA), which tells an agent exactly what data this yields. It does not, however, differentiate itself from near-siblings like meta_get_creative_assets, meta_list_ad_images, or meta_list_ad_videos, which overlap in scope.

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?

The description states what the tool returns but never says when to reach for it versus meta_get_creative_assets or the image/video listing tools. There are no exclusions, prerequisites, or alternative routing hints, leaving the agent to guess among several plausible siblings.

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