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

List targeting criteria for line items in an X Ads account, with options to filter by specific criteria, include soft-deleted records, and paginate results.

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

TableJSON 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

TableJSON 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.

First observedv1.0.1Sep 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond those annotations by noting pagination is preserved and that monetary fields ending in _micro are millionths of the account currency, though 'Native X fields' remains vague.

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?

The description is compact and front-loaded with the core purpose. The second clause about pagination and _micro fields is non-obvious and worth keeping, though the phrase 'Native X fields and pagination are preserved' is grammatically awkward.

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?

Given the annotations, full schema coverage, and an output schema, the description covers the most essential behavioral details but lacks any guidance on when to prefer this tool over related siblings. It is minimally complete but leaves some ambiguity around what 'Native X fields' means.

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 documents every parameter clearly. The description does not repeat or augment the parameter semantics beyond the _micro field convention note, so the baseline of 3 applies.

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 opens with a specific verb and resource: 'List targeting criteria for an ads account's line items'. This clearly identifies the tool's function and distinguishes it from sibling tools like get_targeting_criterion (single record) and search_targeting_* (search-focused).

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?

The description does not provide any when-to-use guidance or mention alternatives such as x_ads_get_targeting_criterion for fetching a single criterion. Usage context is only implied by the word 'List' and the resource phrasing.

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