X Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

x ads list targeting criteria

x_ads_list_targeting_criteria

Read-onlyIdempotent

Lists targeting criteria for an X Ads account's line items so you can audit or refine audience settings, preserving native fields and pagination.

Instructions

List targeting criteria for an ads account's line items Native X fields and pagination are preserved; monetary fields ending in _micro are millionths of the account currency.

Input Schema

Name	Required	Description
`lang`	No	BCP-47 language code; adds a localized_name response attribute for localizable criteria.
`count`	No	Number of records to return per page (1-1000).
`cursor`	No	Pagination cursor from a previous response.
`sort_by`	No	Sort order as attribute-direction, e.g. created_at-asc or updated_at-desc.
`account_id`	Yes	X Ads account ID from X_ADS_ACCOUNT_IDS.
`with_deleted`	No	Include soft-deleted targeting criteria (default false).
`line_item_ids`	Yes	Comma-separated line item IDs to scope the targeting criteria to (the legacy API requires this fi...
`with_total_count`	No	Include the total_count response attribute (default false; exclusive with cursor).
`targeting_criterion_ids`	No	Comma-separated targeting criterion IDs to fetch specific records (max 200).

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.7/5.0

Behavior4/5

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

Annotations already declare readOnly/is idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful domain context not in the annotations: native X fields and pagination are preserved in output, and _micro monetary fields are millionths of the account currency — an important unit caveat for interpreting numbers.

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?

Two compact sentences with the core purpose front-loaded and no wasted text. Minor deduction for the awkward, punctuation-free run-on 'line items Native X fields...' which slightly obscures the sentence boundary.

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 100% parameter documentation, the description need not explain returns; it correctly supplements with the _micro unit convention and pagination-preservation note. The only real gap is the absence of routing guidance to sibling targeting tools.

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% across all 9 params, including cursor, count, sort_by, with_deleted, with_total_count and targeting_criterion_ids, so the schema carries the semantic load. The description only touches the monetary-unit convention and does not add parameter-level meaning, making the baseline 3 correct.

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+resource ('List targeting criteria') scoped to an ads account's line items, which distinguishes it from the singular x_ads_get_targeting_criterion sibling. It does not explicitly contrast with x_ads_search_targeting_interests or x_ads_search_targeting_locations, but the account/line-item framing makes the correct pick inferable.

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 requirement that criteria be scoped by line_item_ids is visible in the schema, so usage is implied, but the description itself gives no when/when-not guidance and never names alternatives (e.g., fetching a single criterion with x_ads_get_targeting_criterion, or searching interests/locations).

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