meta-mcp

Get one ad creative

adcreative_get

Retrieve a specific ad creative by its ID from Meta's Marketing API. Access creative details for your advertisements.

Instructions

GET /{creative_id}.

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": {
      "id": "<id>"
    },
    "name": "adcreative_get"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`fields`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 10, 2026

TDQS

D1.8/5.0

Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as error handling, rate limits, or what happens if the ID is invalid. It only implies a read operation.

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

Conciseness2/5

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

The description is extremely short but not concise in a helpful way; it lacks essential details and is underspecified for a tool with two parameters.

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?

With no output schema, no annotations, and no explanation of parameters or return value, the description is completely inadequate for an agent to correctly invoke or interpret the tool.

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 description coverage is 0%, and the description does not explain the parameters ('id' and 'fields'). The agent is left guessing what 'fields' means or what valid values are.

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 'GET /{creative_id}.' merely states the endpoint, which is a tautology with the title 'Get one ad creative'. It does not explain what an ad creative is or what the tool does beyond an HTTP method.

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?

No guidance on when to use this tool versus siblings like 'adcreatives_list' or 'campaign_get'. It does not specify that it is for a single creative by ID vs listing.

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