Skip to main content
Glama
Sign In
OpenAI Ads MCP

OpenAI Ads MCP

by trakkr-aisearch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_ad

Read-onlyIdempotent

Retrieve an ad's review status and creative metadata using its ad ID.

Instructions

Get one ad by id, including review_status and creative metadata.

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": {
      "ad_id": "<ad_id>"
    },
    "name": "get_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so safety profile is clear. The description adds value by detailing included fields (review_status, creative metadata), which is beyond basic retrieval.

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?

Single sentence, no wasted words. Directly communicates purpose and output content.

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 get-by-ID tool with one parameter and no output schema, the description is mostly complete: it states what it does and what fields are returned. Could mention response format but not critical.

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 0%, so the description must compensate. It states the parameter is the ad's ID, which is minimal. No format, constraints, or source information provided, but for a single string parameter, this meets the baseline.

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 specific verb 'Get' and resource 'ad' with scope 'one ad by id', clearly distinguishing from sibling tools like list_ads. It also specifies included content (review_status, creative metadata).

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 implies use case: to retrieve a single ad by ID. It doesn't explicitly mention when not to use or name alternatives, but the sibling tool list_ads provides a clear contrasting use case.

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