X Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

x ads get line item

x_ads_get_line_item

Read-onlyIdempotent

Retrieve a single X Ads line item by account and line item ID, including native fields and monetary _micro values; optionally include soft-deleted items.

Instructions

Get a single line item by ID Native X fields and pagination are preserved; monetary fields ending in _micro are millionths of the account currency.

Input Schema

Name	Required	Description
`account_id`	Yes	X Ads account ID from X_ADS_ACCOUNT_IDS.
`line_item_id`	Yes	Line item ID belonging to the selected X Ads account.
`with_deleted`	No	Include the line item even if soft-deleted (default false).

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

Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior, so the bar is low, yet the description adds genuinely useful context that the annotations do not: native X fields and pagination are preserved, and monetary fields ending in _micro are in millionths of the account currency. That unit note materially reduces misinterpretation of returned 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?

Two short clauses with no filler, leading with the core action. Minor deduction for the run-on punctuation that makes the second clause read awkwardly.

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 structure need not be explained, and all three params are schema-documented; the description supplies the one thing an agent could misread (the _micro currency units). A brief mention of the soft-delete flag would make it fully 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%, so account_id, line_item_id, and with_deleted are all documented in the schema and baseline 3 applies. The description adds no parameter-level detail beyond the ID concept and does not mention the soft-delete option.

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?

The description gives a specific verb and resource ('Get a single line item by ID'), which cleanly separates it from the list-oriented sibling x_ads_list_line_items. It stops short of naming the sibling, so a 4 rather than a 5.

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?

Usage is only implied: an agent can infer this is the tool for a single known line_item_id versus x_ads_list_line_items, but the description never states that condition or any prerequisite. No explicit when-to-use or when-not guidance is present.

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