MMetadata /docs
⌘K
Docs/Tools/account_level_stats

account_level_stats

Account-level statistics and channel breakdown for a timeframe.

Read analytics

Returns data. Calling it changes nothing, so it is safe in an unattended loop.

What it does

Account-level statistics and channel breakdown for a timeframe.

USE FOR: General account stats by period, channel breakdown, high-level metrics (ROI, spending, leads, opportunities), custom date ranges.
NOT FOR: Campaign-level info (use experiment_performance_stats), specific experiments (use get_experiments).

CHANNELS: FACEBOOK, LINKEDIN, GOOGLE ADS, ALL

TIMEFRAME LOGIC:
- 'quarter'/'Q1-Q4' → timeframe='QUARTER'
- 'week'/'weekly' → timeframe='WEEK'
- ≤3 months → timeframe='MONTH'
- >3 months → timeframe='QUARTER'
- Default: timeframe='MONTH'

CUSTOM DATE RANGE: Provide ONLY startDate + endDate (NO timeframe). Format: ISO 8601 (YYYY-MM-DDTHH:mm:ss.sssZ)

METRICS: impressions, clicks, spent, leads, mqls | opens, sends, actionClicks (CONVO/MESSAGE ads) | triggeredOpps, triggeredOppsAmount, influencedOpps, influencedOppsAmount | triggeredClosedWonOpps, triggeredClosedWonOppsAmount | roiInfluencedOpp, roiTriggeredOpp | cpc, cpl, cpm, ctr, conversionRate | costPerOpen, costPerSend (CONVO/MESSAGE ads) | customFields array

CONVO/MESSAGE AD CAVEAT: opens, sends, actionClicks (and their per-cost derivatives) are the success metrics for CONVO and MESSAGE (LinkedIn message) ad types. clicks/ctr/cpc are typically 0 for these ads — do not treat that as "no performance". If account-level data shows high spend with 0 clicks, drill into experiment_performance_stats or get_ad_details to confirm ad type before drawing conclusions.

Arguments

ArgumentTypeNotes
timeframe string Timeframe for data aggregation. MONTH=monthly breakdown, QUARTER=quarterly breakdown, WEEK=weekly breakdown, YEAR=yearly breakdown. DO NOT use this parameter when providing startDate and endDate.
one of: QUARTER, WEEK, YEAR
startDate string Start date for custom date range in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ). Must be used together with endDate. Do NOT provide timeframe when using this. Example: 2025-07-01T00:00:00.000Z
endDate string End date for custom date range in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ). Must be used together with startDate. Do NOT provide timeframe when using this. Example: 2025-09-30T00:00:00.000Z

Request

curl
curl -s -X POST https://mcp-server.metadata.io/mcp \
  -H "Authorization: $METADATA_PAT" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-11-25" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"account_level_stats","arguments":{}}}'

Response

Real, from the production server, in 619 ms. Values that identify a customer or disclose money are replaced with typed placeholders; keys, types and nesting are exactly as returned.

recorded response
"[value redacted]"

Other analytics tools:

All 160 tools · machine-readable index