X Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

x ads list media library

x_ads_list_media_library

Read-onlyIdempotent

List media library objects in an X Ads account with search, media-type filtering, and cursor pagination to review available creative assets.

Instructions

List the media library objects in 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
`q`	No	Search query matching against name, title, file_name and description.
`count`	No	Number of records to return per page (default 20, max 50).
`cursor`	No	Pagination cursor from a previous response.
`account_id`	Yes	X Ads account ID from X_ADS_ACCOUNT_IDS.
`media_type`	No	Restrict to one media type: IMAGE, VIDEO or GIF.

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds two useful semantic notes — that native X field names and pagination are preserved, and that _micro fields are millionths of the account currency — but does not mention pagination limits, empty-result behavior, or rate limits beyond what the schema implies.

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-loaded, but the two clauses are run together without punctuation ('...in an ads account Native X fields and pagination are preserved'), which forces a second read to parse. The _micro convention note is generic boilerplate rather than media-library-specific.

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, complete parameter documentation in the schema, and annotations carrying the safety profile, the description covers what remains necessary. Only the sibling disambiguation and pagination behavior are missing, and those are modest gaps for a straightforward list operation.

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 q, count, cursor, account_id and media_type are all documented in the schema. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema does the heavy lifting.

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 the media library objects in an ads account'. This clearly distinguishes it from x_ads_get_media_library_item (single-item retrieval) and from other list siblings by resource type, though it does not name an alternative explicitly.

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?

No indication of when to use this versus x_ads_get_media_library_item, x_ads_get_media_upload_status, or x_ads_list_account_posts. The agent must infer selection purely from the tool name.

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