List monitored pages
list_sourcesList the user's monitored pages with their current monitoring and fetch health. Read lastListRead before trusting a page's items to be all of them: coverage "partial" means that check did not cover the list, and itemsRead/pageItems say how far it got. "whole" means the extraction covered the list. It does NOT mean the page is fully stored: itemsRead is what survived the gates below the extractor, so it can sit under pageItems when they refused rows. itemsDropped is how many they refused: itemsRead plus itemsDropped is what the extraction answered, so anything still short of pageItems is what it never answered. That arithmetic needs itemsDropped to be present — a reading that carries itemsRepeated without it predates the field and is a page whose last check is older than it, not a check that refused nothing. itemsDroppedLost splits that total into the part that cost the page a row and the part the pipeline correctly declined (itemsDropped minus it): do not read a high itemsDropped as a problem on its own, because page chrome and rows off the monitoring instructions land there every check and are the pipeline working. itemsDroppedLost is the number to act on, and it is present whenever itemsDropped is, including as 0 — a measured "all of those refusals were correct", so an itemsDropped with no number beside it is a reading older than the field. reason "items_dropped" names the check where they refused every one of them, and itemsRepeated the rows folded into a sibling, which is one part of itemsDropped and not extra to it, and one the lost count does not include since the row is held under the item that claimed its identity. listReadCut is the part of that story lastListRead cannot keep: lastListRead describes only the last check, so it reads unmeasured on a check that did not read the list, while listReadCut stays on a page whose item cap had to be lowered and cut a read, until a whole-page reread that the item cap no longer cuts clears it (absent when no cut is known, which includes a page that is short only because of its own configured cap; get_source describes time and retries; retries counts the whole-page reads spent, and a check that finds the page unchanged reads it whole again until it reaches 3). nextCheckTime is when the next check is expected, and it is ABSENT when there is none to report rather than a time that will never arrive: a page you paused, or one auto-paused after repeated failures, has no check coming at all, and a page whose first check has not landed yet has none to name. Read status to tell those apart — the second is active. effectiveMonitoringFrequency is the cadence in effect, which is slower than the stored monitoringFrequency when that is faster than the scheduler's tick. It does not carry a page's monitoring instructions or sensitivity — call get_source for one page's full settings, and list_source_entries for the items it holds. A page can be empty or shorter than limit while more results remain; continue with pagination.nextCursor until pagination.hasMore is false.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum sources to return (1-100, default 25). | |
| cursor | No | Opaque cursor from the previous response's pagination.nextCursor. |