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

Lists funding instruments (payment sources) for an X Ads account with native fields and pagination; _micro monetary values are millionths of the account currency.

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

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

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

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the description correctly spends its words elsewhere: it discloses that native X fields and pagination metadata are preserved and that '_micro' monetary fields are millionths of the account currency — a non-obvious unit convention an agent cannot infer from annotations or schema.

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?

A single compact statement with the purpose front-loaded and no filler. It is slightly dense — two distinct ideas run together without punctuation — but nothing is wasted.

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 and parameters are fully documented, so the description only needs to add the domain-specific quirks, which it does (payment-source semantics, native field preservation, micro-unit currency). A brief note on paginating via cursor or when to set with_deleted would make it complete.

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% and every parameter (count, cursor, sort_by, with_deleted, with_total_count, funding_instrument_ids) is documented there, so the description adds no parameter meaning of its own. 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 ('List funding instruments (payment sources) for an ads account') and parenthetically clarifies the domain term. No sibling tool covers funding instruments, so differentiation is not required, though it does not explicitly say so.

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?

There is no when-to-use guidance, no mention of the account-scoping prerequisite beyond the 'for an ads account' phrase, and no indication of when to use the filters (with_deleted, funding_instrument_ids) versus listing everything. Usage is only implied by the tool's name and purpose.

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