Skip to main content
Glama
mikusnuz

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_campaigns

Retrieve all ad campaigns within an ad account. Filter results by status (Active, Paused) or marketing objective for targeted campaign analysis.

Instructions

List campaigns in the ad account. Supports filtering by status and objective. Returns paginated results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor for next page
limitNoNumber of results (default 25)
beforeNoPagination cursor for previous page
fieldsNoComma-separated fields to return
statusNoFilter by status: ACTIVE, PAUSED, DELETED, ARCHIVED
objectiveNoFilter by objective: OUTCOME_AWARENESS, OUTCOME_ENGAGEMENT, OUTCOME_LEADS, OUTCOME_SALES, OUTCOME_TRAFFIC, OUTCOME_APP_PROMOTION
account_idNoAd account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.1
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Ad account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.",
+  "type": "string"
+}
  2. First observedv1.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose that results are paginated and that status/objective filtering is supported, which is useful behavioral context, but says nothing about auth/account scoping requirements, rate limits, or default page size behavior beyond what the schema already states.

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?

Three short sentences, front-loaded with the core action and no filler. The final sentence about paginated results is slightly redundant given the after/before/limit parameters, keeping this just short of a 5.

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 7-parameter list tool with no output schema and no annotations, the description covers the essentials (what it lists, filters, pagination) but omits return shape details, default behaviors, and account-scoping caveats. Minimum viable rather than complete.

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?

Schema description coverage is 100%, including a detailed account_id fallback explanation and enum-like status/objective lists, so the schema already documents every parameter. The description only restates the status/objective filters and adds no syntax or format detail beyond the schema, making the baseline 3 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 states a clear verb+resource ('List campaigns in the ad account') and names the two supported filters. It implicitly distinguishes itself from get_campaign/create_campaign by being a listing operation, but does not explicitly route the agent away from siblings like list_adsets or get_campaign.

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?

Filtering by status and objective is mentioned, which implies browsing/filtering use, but there is no explicit when-to-use guidance or comparison against alternatives such as get_campaign (single entity) or the various list_* siblings. Usage context is left to inference.

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