X Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

x ads list funding instruments

x_ads_list_funding_instruments

Read-onlyIdempotent

List payment sources for an X Ads account with pagination and filtering. Retrieve funding instruments by account ID, cursor, or IDs to manage billing options.

Instructions

List funding instruments (payment sources) for an ads account 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
`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 funding instruments (default false).
`with_total_count`	No	Include the total_count response attribute (default false; exclusive with cursor).
`funding_instrument_ids`	No	Comma-separated funding instrument 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

A4.1/5.0

Behavior4/5

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

Annotations already convey read-only, idempotent, non-destructive behavior. The description adds useful context beyond annotations: pagination is preserved and monetary fields ending in _micro are expressed in millionths of the account currency. This helps the agent correctly interpret response values.

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 action and resource. The phrase 'Native X fields and pagination are preserved' is slightly awkward but still short; every clause adds information without redundancy.

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?

Annotations, schema coverage, and output schema all carry substantial weight. The description adds the key non-obvious detail about _micro units and pagination. It does not explain return structure, but that is covered by the output schema, so no critical gap remains.

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 baseline is 3. The description adds no parameter-specific meaning beyond the schema, but it does add context about field units and pagination that indirectly aids parameter interpretation. This meets the baseline without exceeding it.

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 uses a specific verb ('List') and resource ('funding instruments (payment sources)') scoped to an ads account. The parenthetical clarifies the domain term, and the resource name is distinct from all sibling tools, making selection unambiguous.

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

Usage Guidelines4/5

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

The description clearly implies this is the tool for reading payment sources for an ads account, and notes that pagination is preserved. It does not explicitly name alternatives or exclusion conditions, but none of the siblings overlap with funding instruments, so context is sufficient.

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