Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

creatives_list_images

Lists all images uploaded to a Meta Ads account's image library. Use it to review or manage creative assets.

Instructions

List images uploaded to an account's image library.

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": "creatives_list_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It confirms the read-only nature ('List') but omits other behavioral details such as pagination (despite a limit parameter), ordering, or what image metadata is returned. It does not contradict any annotations since none exist.

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, grammatically correct sentence with no fluff or repetition. It efficiently conveys the core function in minimal words, which is appropriate for a straightforward listing tool.

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?

For a simple listing tool with only two parameters and no output schema, the description gives a basic understanding but lacks details such as pagination behavior and the structure of the returned list. It is sufficient for basic selection but not fully informative for an agent needing to anticipate response format or limits.

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

Parameters2/5

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

The schema has 0% description coverage, and the description only hints at the required account_id through 'an account's image library.' The optional limit parameter is not mentioned at all, leaving users to infer its purpose solely from the schema's default value.

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 clearly states the action ('List') and the resource ('images uploaded to an account's image library'), making the tool's purpose immediately obvious. This also distinguishes it from sibling tools like creatives_list_videos, which focus on videos.

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 a use case (retrieving a catalog of images for an account) but provides no explicit guidance on when to choose this tool over alternatives such as creatives_list or creatives_list_videos. No when-not-to-use conditions or alternative names are mentioned.

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