Skip to main content
Glama
get-mcp-ads

ChatGPT Ads MCP server

by get-mcp-ads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

openai ads get conversion insights

openai_ads_get_conversion_insights
Read-onlyIdempotent

Retrieve attributed conversion totals or daily values for an ad account, optionally by country or device, with event details and preserved pagination.

Instructions

Read attributed conversion totals or daily values, optionally by country or device and with event details. Native fields and pagination are preserved. See openai_ads_get_write_schema for nested request fields.

Input Schema

NameRequiredDescriptionDefault
bodyYesExact pinned native JSON request body. Nested configuration objects replace their previous contents, so send the complete intended configuration. Money uses integer account-currency micros.
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. Changed12 schema fields changed
    • addedInput schema / properties / body / properties / attribution_time_basis / anyOf
      Added value: +[
+  {
+    "const": "conversion_time",
+    "type": "string"
+  },
+  {
+    "const": "ad_event_time",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / body / properties / attribution_time_basis / enum
      Removed value: -[
-  "conversion_time",
-  "ad_event_time"
-]
    • removedInput schema / properties / body / properties / attribution_time_basis / type
      Removed value: -"string"
    • changedInput schema / properties / body / properties / attribution_window_days / anyOf
      Previous value: -[
-  {
-    "enum": [
-      7,
-      14,
-      30
-    ],
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "const": 7,
+        "type": "number"
+      },
+      {
+        "const": 14,
+        "type": "number"
+      },
+      {
+        "const": 30,
+        "type": "number"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / body / properties / breakdown / anyOf
      Added value: +[
+  {
+    "const": "device",
+    "type": "string"
+  },
+  {
+    "const": "country",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / body / properties / breakdown / enum
      Removed value: -[
-  "device",
-  "country"
-]
    • removedInput schema / properties / body / properties / breakdown / type
      Removed value: -"string"
    • addedInput schema / properties / body / properties / time_granularity / anyOf
      Added value: +[
+  {
+    "const": "none",
+    "type": "string"
+  },
+  {
+    "const": "daily",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / body / properties / time_granularity / enum
      Removed value: -[
-  "none",
-  "daily"
-]
    • removedInput schema / properties / body / properties / time_granularity / type
      Removed value: -"string"
    • changedInput schema / properties / body / properties / view_through_attribution_window_days / anyOf
      Previous value: -[
-  {
-    "enum": [
-      0,
-      1
-    ],
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "const": 0,
+        "type": "number"
+      },
+      {
+        "const": 1,
+        "type": "number"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • 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

A3.5/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 contributes 'Native fields and pagination are preserved', which usefully signals no result reshaping and paged output, but says nothing about rate limits, result size, or how the pinned native body interacts with reconciliation beyond what the schema states.

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, front-loaded with the core read capability, with no filler. The closing pointer to the write schema is slightly tangential for a read tool but is compact and does not bury the main 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?

An output schema exists, so return-shape explanation is unnecessary, and the nested body semantics are documented in-schema. Given a nested-object read tool with annotations, the description covers scope, optional dimensions, and pagination adequately; only the sibling differentiation is thin.

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%, so the schema already documents adAccountId scoping, include/event_names dependency, breakdown, and granularity. The description restates the breakdown and event-detail options without adding syntax, defaults, or constraints beyond the schema, so 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?

States a specific verb and resource ('Read attributed conversion totals or daily values') plus the supported breakdowns (country/device) and the optional event-detail expansion. It doesn't explicitly contrast itself with the sibling openai_ads_get_insights or openai_ads_get_conversion_events, so the boundary with those tools is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The breakdown and include options imply when this tool is appropriate, but there is no explicit 'use this instead of X when Y' guidance against the many sibling read tools. The only routing pointer is to openai_ads_get_write_schema for nested request fields, which addresses schema discovery rather than tool selection.

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