Skip to main content
Glama
flin-agency

flin-meta-ads-mcp

by flin-agency

list_ad_creatives

Fetch ad creatives from a Meta ad account with customizable fields and effective status filters. Retrieve a list of creatives to inspect or download advertising assets.

Instructions

List ad creatives for an ad account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNo
limitNo
fieldsNo
ad_account_idNo
effective_statusNo
Behavior2/5

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

The description only says 'List', which implies a non-mutating read, but provides no behavioral details beyond that. With no annotations provided, the description carries the full burden but fails to mention pagination, authorization requirements, or any side effects.

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 concise sentence that avoids fluff and directly states the operation. It is front-loaded with the verb and resource, making it easy to scan, though the brevity limits other aspects.

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 5 parameters, no output schema, and no annotations, this description is far from complete. It omits essential context like filtering via 'effective_status', field selection via 'fields', and pagination through 'after' and 'limit', leaving the agent with insufficient information to invoke correctly.

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% and none of the 5 parameters ('after', 'limit', 'fields', 'ad_account_id', 'effective_status') are explained in the description. The tool's actual filtering and pagination capabilities are entirely undocumented.

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 uses a specific verb ('List') and resource ('ad creatives') with scope ('for an ad account'), clearly distinguishing it from sibling tools like 'get_ad_creative' (single retrieval) or 'list_ad_images' (different resource). The purpose is immediately understandable.

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 is provided on when to use this tool compared to alternatives such as 'list_ads' or 'get_ad_creative'. There is no mention of exclusions, prerequisites, or typical scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/flin-agency/flin-meta-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server