devtune_get_404_demand
Get project-scoped 404 Demand for one published window, separated into credible content-intent clusters and likely scanner or technical noise, with materialization state, machine-traffic sensor coverage, and inferred project relevance. windowDays 30 (default) is the window opportunities and actions use; 7 is mined from the same run over the last seven days, so its clusters, counts and ranking are its own. window gives the selected start and end dates and asOf, when the run that mined the clusters finished. window.coverage is read live when you call, with its own observedAt: coveredDays counts the days a crawler sensor that reports status codes recorded machine traffic. Hours recorded after asOf can raise it while the clusters stay as mined, so do not treat the two as one snapshot. Fewer covered days than windowDays means part of the window is unmeasured, not free of 404s. A null window with dataAvailability degraded means that window is not published, including after a failed run, which state still reports. Clusters prioritize project fit before request volume; unrelated demand remains visible but is excluded from automatic action suggestions. Optional hosts list each cluster's request counts for the 20 busiest request hosts across the window; a null host counts requests whose host is unknown or outside those hosts. When the window includes 404s from a source that reports page views only and cannot verify requests, the response names that source, its hosts and the qualifiers, and each cluster lists which of its hosts they came from; provenance with state unavailable means that could not be checked.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "devtune_get_404_demand"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| windowDays | No | Published 404 Demand window in days: 7 or 30. Defaults to 30. |