Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by anhnguyen0905
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_ads

Read-onlyIdempotent

Retrieve ad identifiers, names, statuses, and parent IDs for ads under a specified account, campaign, or ad set. Use this to inspect ad hierarchy.

Instructions

Get ads beneath an account, campaign, or ad-set parent.

Args: params: Parent object ID, maximum result count, and JSON or Markdown response format.

Returns: A rendered {"success": bool, "data": list[object] | null, "error": string | null} envelope containing ad identifiers, names, statuses, ad-set IDs, and campaign IDs.

Use this to inspect ads for a known hierarchy parent. Do not use it for performance metrics or to create, edit, pause, or delete ads.

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": {
      "params": "<params>"
    },
    "name": "get_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds valuable context about the return envelope structure and the fields returned, which goes beyond the annotations. No contradictions.

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 two concise paragraphs plus a usage note. It front-loads the core purpose and includes only essential information. No redundant or unnecessary sentences.

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

Completeness4/5

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

Given the presence of an output schema and rich annotations, the description covers the tool's purpose, usage boundaries, and basic parameters. It explains the return envelope and fields. However, it does not mention pagination behavior beyond the limit parameter, which is a minor gap.

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?

The input schema includes descriptions for all three parameters (parent_id, limit, response_format), so the schema already covers parameter semantics. The description summarizes them briefly ('Parent object ID, maximum result count, and JSON or Markdown response format') but adds no additional meaning beyond what is in the schema. Baseline 3 is appropriate.

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 ('get') and resource ('ads beneath an account, campaign, or ad-set parent'), clearly distinguishing it from sibling tools like get_campaigns and get_insights. It explicitly states the scope ('beneath a parent'), making the purpose unambiguous.

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?

The description clearly states when to use the tool ('inspect ads for a known hierarchy parent') and when not to ('Do not use it for performance metrics or to create, edit, pause, or delete ads'). However, it does not explicitly name alternative tools for those uses, though siblings like get_insights are implied.

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