Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cloudx.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Examples

These examples use the real tool names exposed by CloudX MCP. Reporting examples use exact UTC timestamps.

​
Example 1: Dashboard Summary For US iOS Traffic

Question: 
Show me dashboard performance for US iOS production traffic from April 15, 2026 through April 21, 2026. Summarize revenue, fill rate, CTR, and daily trend.
Tool call: 
{
  "name": "GetReportDashboard",
  "arguments": {
    "start_time": 1776211200,
    "end_time": 1776815999,
    "country": "US",
    "device_os": "iOS",
    "test_mode": "production"
  }
}
What you can expect back:
  • a summary object for totals and derived KPIs
  • a chart_data array with daily rows for the selected period

​
Example 2: Compare Bidders On Android Test Traffic

Question: 
For April 15, 2026, compare bidder performance on Android test traffic in the US. Rank bidders by revenue and call out bid rate and win rate.
Tool call: 
{
  "name": "GetReportBidders",
  "arguments": {
    "start_time": 1776211200,
    "end_time": 1776297599,
    "country": "US",
    "device_os": "Android",
    "test_mode": "test"
  }
}
Typical fields:
  • name
  • requests
  • bids
  • bid_rate
  • impressions
  • win_rate
  • revenue
  • ecpm

​
Example 3: Inspect Banner Placements For One App

Question: 
Show banner ad unit performance for com.example.game in the US on Android for April 15, 2026. I want to find the weakest placements by fill rate.
Tool call: 
{
  "name": "GetReportAdUnits",
  "arguments": {
    "start_time": 1776211200,
    "end_time": 1776297599,
    "country": "US",
    "device_os": "Android",
    "test_mode": "all",
    "app_bundle": "com.example.game",
    "ad_unit_type": "BANNER"
  }
}
Use this pattern when you already know the app bundle or want one ad format only.

​
Example 4: Export Rows For Analysis

Question: 
Export CloudX report rows for US Android traffic from April 1, 2026 through April 7, 2026 so I can inspect the raw table structure.
Tool call: 
{
  "name": "GetReportExport",
  "arguments": {
    "start_time": 1775001600,
    "end_time": 1775606399,
    "country": "US",
    "device_os": "Android"
  }
}
This tool returns a JSON shape with:
  • columns
  • rows
  • row_count

​
Example 5: Search CloudX Documentation

Question: 
Find CloudX docs about report filters and summarize which filters are available.
Tool call: 
{
  "name": "SearchDocs",
  "arguments": {
    "body": {
      "query": "report filters"
    }
  }
}
This tool returns matching docs pages with:
  • content
  • path
  • url
  • metadata

​
Prompting Tips

  • ask one reporting question per tool call when possible
  • use exact dates such as April 15, 2026 instead of last week
  • specify country, device_os, and test_mode when you need a narrow answer
  • use GetReportExport when you want rows, not a narrative summary
  • use GetReportDashboard first when you need a fast overall health check
  • use SearchDocs first when your question is about CloudX setup, configuration, or feature behavior