meta-mcp

List ad creatives under an ad account

adcreatives_list

Retrieve ad creatives for a Meta ad account. Specify fields and paginate results.

Instructions

GET /act_{id}/adcreatives.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_id": "<account_id>"
    },
    "name": "adcreatives_list"
  }
}

Input Schema

Name	Required	Description	Default
`account_id`	Yes
`fields`	No
`limit`	No
`auto_paginate`	No
`max_pages`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 10, 2026

TDQS

D1.3/5.0

Behavior1/5

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

No annotations are provided, and the description minimally indicates it's a GET request (read operation), but does not disclose any behavioral traits such as rate limits, pagination behavior, or data scope. The agent has no insight into side effects or constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief but not concise in a helpful way; it omits critical information. Every sentence should earn its place, but this single sentence provides minimal value and could be expanded significantly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of 5 parameters, no output schema, no annotations, and many sibling tools, the description is severely incomplete. It does not explain return values, pagination, or how it differs from similar list tools, leaving the agent underinformed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, meaning no parameter descriptions in the schema. The description adds no information about parameters (e.g., account_id format, fields usage, limit behavior), so it fails to compensate for the lack of schema documentation.

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

Purpose2/5

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

The description is just the endpoint path 'GET /act_{id}/adcreatives.' which barely adds any meaning beyond the title 'List ad creatives under an ad account.' It does not explain what ad creatives are or what listing entails, making it only slightly better than a tautology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus sibling tools like adsets_list or campaigns_list. There is no mention of prerequisites, context, or exclusions, leaving the agent without decision-making support.

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