X Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

x ads get media library item

x_ads_get_media_library_item

Read-onlyIdempotent

Retrieve a specific media library item by media key to access its details while preserving native X fields and pagination.

Instructions

Get a single media library object by media key Native X fields and pagination are preserved; monetary fields ending in _micro are millionths of the account currency.

Input Schema

Name	Required	Description	Default
`media_key`	Yes	Uploaded media key registered in the selected account's media library.
`account_id`	Yes	X Ads account ID from X_ADS_ACCOUNT_IDS.

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

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description still adds genuinely useful context not in the annotations: native X fields are preserved, and monetary fields ending in _micro are millionths of the account currency — a non-obvious unit convention an agent would otherwise misinterpret.

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-loads the action, but the sentence runs on without punctuation — 'by media key Native X fields and pagination are preserved' reads ambiguously, as if 'Native X fields' were part of the lookup rather than a separate note. Size is right; the structure is sloppy.

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 carries return-value detail, and the input schema documents both required parameters, so little is missing. The only loose end is the mention of pagination for a single-item fetch, which is unexplained and mildly confusing.

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%, with both required parameters fully documented (media_key and account_id including the X_ADS_ACCOUNT_IDS source). The description adds nothing beyond repeating 'by media key', so the 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+resource (get a single media library object) and the key used to identify it. It does not explicitly name x_ads_list_media_library as the alternative, but the singular-vs-list contrast is easy to infer from the sibling names.

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?

Implied usage only: retrieve one item when the media_key is already known. There is no explicit statement of when to use this instead of x_ads_list_media_library or x_ads_get_media_upload_status, and no preconditions such as whether the key must belong to the given account.

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