Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_adsets

List ad sets in a Meta ad account, optionally filtered by campaign or status, supporting pagination.

Instructions

List ad sets in the ad account. Optionally filter by campaign or status.

Input Schema

NameRequiredDescriptionDefault
afterNoPagination cursor for next page
limitNoNumber of results (default 25)
fieldsNoComma-separated fields to return
statusNoFilter by status: ACTIVE, PAUSED, DELETED, ARCHIVED
account_idNoAd account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.
campaign_idNoFilter by campaign ID

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.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a safe read via 'List' but says nothing about pagination semantics, permission/auth requirements, defaults, or what is returned for a 6-parameter listing tool.

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?

Two short sentences with the resource and filters front-loaded; there is no filler. It is appropriately sized, though it could carry a bit more signal without bloat.

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 paginated listing tool with no annotations and no output schema, the description is minimally adequate: the rich schema covers inputs, but return shape and pagination behavior must be inferred from parameter names alone.

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%, so all six parameters are already documented in the schema, including the account_id env-var fallback and status values. The description only restates the campaign/status filters and adds no new parameter semantics, so baseline 3 applies.

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?

States a specific verb+resource ('List ad sets') with a scoping clause ('in the ad account'), which distinguishes it from generic siblings. It does not explicitly contrast with near-neighbors like get_campaign_adsets or list_ads, but the purpose is unambiguous.

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?

'Optionally filter by campaign or status' implies usage contexts, but there is no explicit when-to-use guidance and no mention of alternatives such as get_campaign_adsets or get_adset. Usage must be inferred.

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