Skip to main content
Glama
pauloFroes

mcp-meta-marketing

by pauloFroes

List Ad Sets

list_adsets
Read-only

List ad sets from your Meta ad account, optionally filtering by campaign ID or effective status. Returns key details like targeting, budgets, and schedules, auto-paginating results.

Instructions

List ad sets in the ad account. Optionally filter by campaign ID or effective status. Returns ad set name, status, targeting, budget, and schedule. Auto-paginates up to 10 pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoItems per page (default: 100, max: 100)
fieldsNoComma-separated fields. Default: id,name,status,effective_status,campaign_id,daily_budget,lifetime_budget,targeting,optimization_goal,billing_event,start_time,end_time
campaign_idNoFilter ad sets by campaign ID. If set, queries /{campaign_id}/adsets instead of account-level.
effective_statusNoFilter by effective status
Behavior5/5

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

Description discloses that it auto-paginates up to 10 pages and returns specific fields (name, status, targeting, budget, schedule), which goes beyond the annotations' read-only and non-destructive hints. No contradiction with annotations.

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?

Four short sentences, front-loaded with the action, no filler. Every sentence adds value, including pagination and return fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description covers purpose, optional filters, return fields, and pagination behavior. Combined with strong annotations, this is a complete description for a list tool.

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 covers 100% of parameters with descriptions; the description only reiterates the filter options without adding new semantics. Baseline 3 applies as schema does the heavy lifting.

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?

Clearly states it lists ad sets in the ad account, with a specific verb and resource. Distinguishes from sibling tools like list_campaigns and list_ads by naming the resource type. The optional filters add further specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context: use when you need to list ad sets, optionally filtering by campaign ID or effective status. However, it does not explicitly mention when not to use it or name alternatives, so it stops short of a 5.

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/pauloFroes/mcp-meta-marketing'

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