Skip to main content
Glama
Sign In
get-mcp-ads

X Ads by Get MCP Ads

by get-mcp-ads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

x ads list post previews

x_ads_list_post_previews
Read-onlyIdempotent

Retrieve rendered HTML previews for published, scheduled, or draft X Ads posts by account and post IDs while preserving native X fields and pagination.

Instructions

Get rendered HTML previews for published or scheduled posts Native X fields and pagination are preserved; monetary fields ending in _micro are millionths of the account currency.

Input Schema

NameRequiredDescriptionDefault
user_idNoPromotable user the posts belong to (defaults to the account's own user); needed when previewing ...
tweet_idsYesComma-separated post IDs (or scheduled post IDs, per tweet_type) to preview (max 200).
account_idYesX Ads account ID from X_ADS_ACCOUNT_IDS.
tweet_typeYesType of the IDs in tweet_ids.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal 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.

  1. Changed2 schema fields changedv1.1.1
    • 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"
+  }
+]
  2. First observedv1.0.1

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, openWorld, so the safety profile is covered. The description adds genuinely useful context that monetary fields suffixed _micro are millionths of the account currency and that native X fields and pagination are preserved — but it omits the 200-ID cap and the DRAFT case, both of which affect correct invocation.

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?

Appropriately short, and the purpose is front-loaded. But the second clause runs on without punctuation and reads as a spliced fragment ('...scheduled posts Native X fields and pagination are preserved'), forcing a re-read.

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, so return values need not be explained, and the description covers the one non-obvious output convention (_micro currency units). The main gap is that the stated scope ('published or scheduled') fails to mention the DRAFT option the required tweet_type parameter supports.

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%, including the tweet_type enum, the 200 max on tweet_ids, and the user_id default, so the schema already carries parameter meaning. The description's only param-adjacent contribution is the _micro convention, which concerns returned values rather than inputs — 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 ('Get rendered HTML previews for ... posts'), which distinguishes it from the sibling list/get post tools that return post data rather than rendered previews. However, it says 'published or scheduled' while the required tweet_type enum also accepts DRAFT, so the stated scope is narrower than the tool's actual capability.

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 guidance on when to choose this over x_ads_list_promoted_posts, x_ads_get_promoted_post, or x_ads_list_account_posts, and no prerequisites stated. The agent must infer the preview-vs-metadata distinction entirely from the tool name and one-line purpose.

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

Deploy Server

Other Tools