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 creative assets

meta_get_creative_assets
Read-onlyIdempotent

Retrieve ad-linked creative assets with actual ad names, collection covers, carousel components, resolved image hashes, and video URLs, while classifying catalog-only ads separately.

Instructions

Return ad-linked creative media with actual ad names, collection covers, all carousel/flexible components, resolved image hashes and video URLs. Catalog-only ads are classified separately; use the hosted GetMCPAds service for an interactive visual gallery. Raw creative metadata remains available for diagnostics.

Input Schema

NameRequiredDescriptionDefault
adIdsNoSpecific ad IDs to enrich.
limitNoMaximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
cursorNoPagination cursor from previous response
adAccountIdNoAd account ID. Used when adIds/creativeIds are omitted.
creativeIdsNoSpecific creative IDs to enrich.

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so safety behavior is largely covered. The description adds useful context about returned media components, separate catalog-only classification, and availability of raw creative metadata for diagnostics, though it does not discuss permissions or rate limits.

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 three sentences and front-loads the core return content. Each sentence provides useful context, though the hosted gallery mention is somewhat tangential and could be trimmed if space were at a premium.

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?

With complete schema descriptions, rich annotations, and an output schema, the description provides enough behavioral and output context for an agent to call the tool correctly. It does not need to explain return values in detail because the output schema exists.

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?

The input schema has 100% description coverage and clearly documents all five parameters, including adIds, creativeIds, adAccountId, limit, and cursor. The description does not add meaning beyond the schema for these parameters, so the baseline of 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?

The description uses a specific verb and resource: it returns ad-linked creative media and enumerates the included asset types such as collection covers, carousel components, image hashes, and video URLs. It separates catalog-only ads and mentions the hosted gallery alternative, though it does not explicitly distinguish itself from the sibling meta_get_creatives tool.

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?

It gives clear context for using the hosted GetMCPAds service for an interactive visual gallery and implies this tool is for raw diagnostic metadata, but it does not state when to choose this over sibling tools such as meta_get_creatives, meta_list_ad_images, or meta_list_ad_videos. Usage is therefore implied rather than fully guided.

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