list_tasks
Read what needs the person now: one list of tasks across their websites, such as missing links, pages that are down, disavow uploads, renewals, plan and payment problems, Search Console reconnects, agent access requests and setup. Each task says who can act, how it clears, where in the console it gets done and what an agent may do; agents draft outreach and never send it. Call it at the start of a session.
This command name is absent from deployment evidence dated 2026-09-20. Hosted availability for this current definition is unverified; inspect your connected catalog before invoking it. Verify the command and its input schema in the selected environment.
This read does not start a verification job.
Example request
Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.Returned result
Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data instructuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.
Full response example
Full response example
Input fields
Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.Validation and omitted values
Omit projectId to cover every website the credential can read, up to 200; truncated tells you when more websites exist. You can also supply one accessible website id. Selecting one website does not exclude eligible workspace tasks for plan limits, payment, agent access requests or connecting an agent. Read scopes and who can act still apply. Each task covers one kind of work for one website or the workspace. It names who can act (you, owner, agent_or_you or only_you), whether the person behind this credential can act (canAct, from their workspace role), how it clears and the console route for the work. The list sorts by priority (urgent, normal, low, setup), then oldest since, then website. A provider reconnect task covers one website; count is its connections that need a new sign-in, and since is their oldest update time. The service derives tasks from saved records on each read; it stores no task and marks none done. A task clears when saved data shows the work happened (a check, a sync or a provider event), or after a deliberate action such as pausing checks or rejecting a suggestion. Missing and can’t-reach use the same link statuses as get_link_summary; the low cant_reach_lasting task uses the same inclusive seven-day cutoff, rounded down to the hour, as the link-list filter. agent.can describes task capability; follow-up commands still require their own access. agent.prompt is a sentence the person can paste; agent.steps lists the exact commands, or get_handoff supplies them when handoff names one. Finish with the verify step. Agents draft outreach and never send it. Each kind requires its read scope; payment problems and setup suggestions appear only to members who can act on them.Output fields
Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.tasks(array, required).counts(object, required): additional fields rejectedgeneratedAt(string, required).truncated(boolean, required): True when the workspace has more than 200 readable websites and only the first 200 were read.
All fields and nested objects
All fields and nested objects
Errors and retries
Follow the error recovery before retrying this read. Preserve the selected workspace, project, filters and feed. Recovering a read does not require an idempotency key or another verification job. Operation-specific errors includeINVALID_INPUT, PROJECT_NOT_FOUND, WORKSPACE_ACCESS_DENIED, INSUFFICIENT_SCOPE.
See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.