X Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

x ads get campaign

x_ads_get_campaign

Read-onlyIdempotent

Retrieves a single X Ads campaign by account ID and campaign ID, returning native X fields and micro-currency values for accurate campaign review.

Instructions

Get a single campaign by ID Native X fields and pagination are preserved; monetary fields ending in _micro are millionths of the account currency.

Input Schema

Name	Required	Description
`account_id`	Yes	X Ads account ID from X_ADS_ACCOUNT_IDS.
`campaign_id`	Yes	Campaign ID belonging to the selected X Ads account.
`with_deleted`	No	Include the campaign even if soft-deleted (default false).

Output Schema

Name	Required	Description	Default
`result`	Yes	Original 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.

Changed2 schema fields changedv1.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

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"
+  }
+]

First observedv1.0.1Sep 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuine context beyond them: that native X fields and pagination are passed through unchanged and that _micro monetary fields are millionths of the account currency, which an agent needs to interpret values correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is short and front-loads the purpose, but the sentences are run together without punctuation ("by ID Native X fields..."), which blunts readability of the units caveat. Every clause is useful; the structure is the weak point.

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 an output schema present and rich annotations, the description needn't describe return shape, and it does supply the one interpretive detail the schema can't convey (the _micro unit convention). Only the absence of routing guidance toward the list sibling keeps it from a 5.

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%, covering account_id, campaign_id and the with_deleted default, so the baseline is 3. The description only echoes the by-ID semantics and adds nothing about with_deleted or the account scoping beyond what the schema states.

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?

"Get a single campaign by ID" gives a specific verb (get), resource (campaign) and scope (single, by ID), which implicitly separates it from the sibling x_ads_list_campaigns. It does not explicitly name the sibling, so it falls just short of a 5.

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?

Usage is only implied: an agent infers it should call this when it already holds a campaign_id and wants one record rather than a list. There is no explicit when-to-use/when-not, no mention of prerequisites, and no pointer to x_ads_list_campaigns as the alternative.

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