Skip to main content
Glama

Ads Uploader: Meta Ads MCP

Get Ad Set Details

ads_get_adset
Read-onlyIdempotent

Read ONE Meta ad set's settings and full targeting, including included and excluded custom audiences. Read before copying or duplicating an ad set.

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": {
      "accountId": "<accountId>",
      "adSetId": "<adSetId>"
    },
    "name": "ads_get_adset"
  }
}

Input Schema

NameRequiredDescriptionDefault
adSetIdYesONE Meta ad set ID.
accountIdYesAd account ID, e.g. act_123.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, closed-world), so the description's job is to add content detail; it does so by promising full targeting including included and excluded custom audiences, which is consequential information for a duplication workflow. It omits return shape nuances and failure modes, but that is minor given the annotation coverage.

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?

Two short sentences, front-loaded with what is read and what it contains, then immediately followed by the workflow trigger. No filler words or redundant restatement of the title.

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?

For a simple two-parameter read with no output schema, the description conveys the key content (settings plus full targeting, including excluded audiences) and the reason to call it. Only minor gaps remain, such as how large or nested the targeting payload may be.

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% with only two required parameters, so the schema already explains that adSetId is a single ad set ID and accountId is an ad account ID. The description reinforces the 'ONE' constraint but adds no format or edge-case guidance beyond the schema; 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?

Uses a specific verb and resource ('Read ONE Meta ad set's settings and full targeting') and the emphasis on 'ONE' implicitly separates it from list-style siblings such as ads_list_adsets. It does not explicitly name an alternative tool, but the scope of a single ad set is unmistakable.

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?

Gives an explicit workflow cue — 'Read before copying or duplicating an ad set' — which tells the agent when this tool is the right prerequisite step. It offers no when-not-to-use condition or named alternative for retrieving broader listing data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.