Skip to main content
Glama
ChatGPT Ads MCP server

ChatGPT Ads MCP server

by get-mcp-ads

openai ads get conversion pixels

openai_ads_get_conversion_pixels
Read-onlyIdempotent

Retrieve an ad account's conversion pixels and connected pixel IDs, with native fields and pagination preserved for tracking setup and review.

Instructions

List the account's conversion pixels and connected pixel IDs. Native fields and pagination are preserved. See openai_ads_get_write_schema for nested request fields.

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": {
      "adAccountId": "<adAccountId>"
    },
    "name": "openai_ads_get_conversion_pixels"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoDocumented native query parameters. Each call reads one page unless the tool says otherwise.
adAccountIdYesThe adacct_ ID configured in OPENAI_ADS_ACCOUNT_ID. The API key is scoped to this one account; another ID is refused.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / query / properties / order / anyOf
      Added value: +[
      +  {
      +    "const": "asc",
      +    "type": "string"
      +  },
      +  {
      +    "const": "desc",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / query / properties / order / enum
      Removed value: -[
      -  "asc",
      -  "desc"
      -]
    • removedInput schema / properties / query / properties / order / type
      Removed value: -"string"
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds that native fields and pagination are preserved, a useful note about response shape, but says nothing further about page size, ordering, or how many pixels a typical account returns. With annotations carrying the safety burden, a 3 is appropriate.

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?

Three short sentences with the purpose front-loaded. The trailing write-schema pointer is the one sentence that does not clearly earn its place for a read tool, though it is brief.

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

Completeness3/5

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

An output schema exists and annotations cover safety, so the core is complete enough to call. However, the description never explains how the returned pixel IDs relate to conversion_events or conversion_settings, and its only external pointer targets the mutation schema, leaving the agent without relational context for a tool that sits in a crowded conversion-related namespace.

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% — adAccountId's pattern and account-scoping constraint are fully documented in the schema, as are the query paging parameters. The description adds no parameter-level meaning, so the baseline 3 applies; the cross-reference to openai_ads_get_write_schema does not clarify the read parameters.

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?

States a specific verb and resource — list the account's conversion pixels plus connected pixel IDs — which an agent can distinguish from conversion_events or conversion_settings siblings by name. It stops short of explicitly contrasting with those siblings, but the resource is unambiguous.

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?

There is no guidance on when to choose this over openai_ads_get_conversion_events or openai_ads_get_conversion_settings, which cover adjacent concepts. The only routing hint points to openai_ads_get_write_schema, a write-oriented sibling, for nested request fields — a confusing pointer for a read-only listing tool.

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