MCP server
get_website_daily_stats
Returns one row per day for a website (default the last 30 days, every day included even with 0): date (YYYY-MM-DD, UTC), leadsIdentified, avgIcpScore and leadsWithIcpScore.
Get daily lead counts · Read-only
Returns one row per day for a website (default the last 30 days, every day included even with 0): date (YYYY-MM-DD, UTC), leadsIdentified, avgIcpScore and leadsWithIcpScore. Each lead is counted on the day of its most recent visit, so a returning lead moves to its latest day. leadsProspected, emailsSent and emailsScheduled are always 0 here. For the audience breakdown use get_website_analytics. websiteId comes from list_websites.
| Connection | Account URL, team member URL or OAuth |
|---|
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
websiteId | string | Yes | Website ID from list_websites. |
dateFrom | string | No | Start date, e.g. 2026-10-01 (ISO), 10/01/2026 or epoch milliseconds. Only used when dateTo is also given; otherwise the last 30 days. |
dateTo | string | No | End date (inclusive), same formats as dateFrom. Only used together with dateFrom. |
Tool definition
What your assistant receives from tools/list:
{
"name": "get_website_daily_stats",
"title": "Get daily lead counts",
"annotations": {
"title": "Get daily lead counts",
"readOnlyHint": true,
"destructiveHint": false,
"idempotentHint": true,
"openWorldHint": false
},
"inputSchema": {
"type": "object",
"properties": {
"websiteId": {
"type": "string",
"description": "Website ID from list_websites."
},
"dateFrom": {
"type": "string",
"description": "Start date, e.g. 2026-10-01 (ISO), 10/01/2026 or epoch milliseconds. Only used when dateTo is also given; otherwise the last 30 days."
},
"dateTo": {
"type": "string",
"description": "End date (inclusive), same formats as dateFrom. Only used together with dateFrom."
}
},
"required": [
"websiteId"
]
}
}