meta-mcp

List ad sets

adsets_list

Retrieve ad sets from a specified Meta Ads account or campaign. Supports filtering by fields, status, and pagination controls.

Instructions

GET /{parent}/adsets. parent.type selects the path: 'account' → /act_{id}/adsets, 'campaign' → /{campaign_id}/adsets.

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": {
      "parent": "<parent>"
    },
    "name": "adsets_list"
  }
}

Input Schema

Name	Required	Description	Default
`parent`	Yes
`fields`	No
`filtering`	No
`effective_status`	No
`limit`	No
`auto_paginate`	No
`max_pages`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 10, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Without annotations, the description must convey behavioral traits, but it only provides the HTTP method and path. No mention of pagination, filtering behavior, error handling, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise but under-specified. It front-loads the URL structure but omits necessary details. Appropriate length for what it contains, but not optimally helpful.

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 7 parameters, nested objects, no output schema, and no annotations, the description is severely incomplete. An agent would lack critical information to use the tool 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 the description adds no semantics for parameters like fields, filtering, effective_status, limit, auto_paginate, or max_pages. Only the parent parameter is partially explained via URL path.

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 HTTP method (GET) and resource (adsets) with specific path construction for two parent types. It distinguishes from sibling tools like ads_list, campaigns_list, etc.

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 explicit guidance on when to use this tool compared to alternatives. The description only explains URL structure without context on selecting parent type or other usage notes.

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