Skip to main content

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:
Tool call:
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:
Tool call:
Typical fields:
  • name
  • requests
  • bids
  • bid_rate
  • impressions
  • win_rate
  • revenue
  • ecpm

Example 3: Inspect Banner Placements For One App

Question:
Tool call:
Use this pattern when you already know the app bundle or want one ad format only.

Example 4: Export Rows For Analysis

Question:
Tool call:
This tool returns a JSON shape with:
  • columns
  • rows
  • row_count

Example 5: Search CloudX Documentation

Question:
Tool call:
This tool returns matching docs pages with:
  • content
  • path
  • url
  • metadata

Example 6: Build A Custom Country Breakdown

Question:
Tool call:
The response identifies the requested dimensions and metrics, then returns grouped values in rows.

Example 7: Inspect An Auction And Its Bids

Start by finding recent auctions:
Then pass an auction_id from the result to GetAuctionShow:
Use GetAuctionRounds for aggregate round metrics and GetAuctionBids when you need to search bid rows across many auctions.

Example 8: Review A/B Test Performance

Compare control and test cumulative and daily metrics. Treat statistical fields as unavailable when they are omitted or null.

Example 9: Edit, Validate, And Publish Configuration

First inspect the live configuration with GetConfigShow and use the returned resource IDs. This example changes one ad unit’s floor in a draft:
Ordinary edits return a draft id and validation result. Review that draft directly:
Validate it again if needed, then publish only after review:
Publishing changes the live account configuration. Use the actual draft ID returned by PostConfigEdit, and confirm the validation result before publishing.

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 GetReportBreakdown when the fixed report tools do not provide the grouping you need
  • use GetAuctionList before GetAuctionShow when you do not know the auction ID
  • ask the client to show and validate a config draft before calling PostConfigPublish
  • use SearchDocs first when your question is about CloudX setup, configuration, or feature behavior