Skip to main content
Glama

Metadata MCP Connector

Get Ad Details

get_ad_details
Read-only

Read an advertising-library ad by ID. Returns its configuration, content, creative references, channel, and status as available from the platform, or an error when the ad is inaccessible. This is an ad definition, not an experiment performance report. Its status is the library status (active or archived), not whether the ad is on or off inside an ad set: list_experiment_ads gives that for the ad sets of given experiments or campaigns.

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": {
      "ids": "<ids>"
    },
    "name": "get_ad_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesAd ID(s) to get details for. Can be: single integer (182124) or comma-separated string ('182124,182123').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered; the description adds that missing or inaccessible ads produce an error. It also clarifies a subtle semantic trait: the returned status is library status (active/archived), not in-ad-set delivery status. It does not disclose behavior for comma-separated multi-ID calls (partial failures, ordering) 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.

Conciseness4/5

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

Front-loaded with the verb and resource, then return contents, then disambiguation. Every sentence carries information, though the final sentence is long and packs two distinct status concepts together, which slightly reduces scannability.

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?

With no output schema, the description correctly takes on the burden of describing return contents and error behavior, and it heads off the most likely misinterpretation of the status field. It stops short of explaining multi-ID response shape or per-ID error handling, which is the remaining gap for a batching-capable read 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 coverage is 100% and the ids property already documents both the single-integer and comma-separated-string forms with an example. The description adds nothing about the ids parameter, so the baseline 3 applies.

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?

"Read an advertising-library ad by ID" gives a specific verb and resource, then enumerates what comes back (configuration, content, creative references, channel, status). It explicitly contrasts itself with an experiment performance report, so an agent can separate it from list_experiment_ads without opening either schema.

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 states the key selection rule: this tool gives the ad definition and library status, whereas list_experiment_ads gives on/off status inside ad sets of given experiments or campaigns. That resolves the most likely confusion. It offers no guidance on when to prefer it over creative-fetching or create/update siblings, and no prerequisites are mentioned.

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.

Resources