experiments_keywords_stats
Keyword performance data from active experiments with date range filtering.
Read search
Returns data. Calling it changes nothing, so it is safe in an unattended loop.
What it does
Keyword performance data from active experiments with date range filtering. USE FOR: Keyword performance across experiments, Google Ads keyword metrics/trends, keyword ROI and conversions, search term effectiveness. REQUIRED: Date range in YYYY-MM-DD to YYYY-MM-DD format.
Arguments
| Argument | Type | Notes | |
|---|---|---|---|
startDate |
string | required | Start date in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ). Example: '2025-01-01T00:00:00.000Z' |
endDate |
string | required | End date in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ). Example: '2025-12-31T23:59:59.999Z' |
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":"experiments_keywords_stats","arguments":{"startDate":"<startDate>","endDate":"<endDate>"}}}'
Response
Recorded with these arguments. Enum values are the first the tool's own schema
declares; ids were fetched live from a list_ call immediately before.
arguments used
{
"startDate": "2026-08-06T17:01:08.920Z",
"endDate": "2026-09-05T17:01:08.920Z"
}
Real, from the production server, in 1574 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]"
Related
Other search tools: