Skip to main content
list_workspace_events Read workspace limit changes with before/after values and a separate stable cursor. Requires a workspace-wide grant; project-limited grants cannot read this feed.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.
This read does not start a verification job. Process every event before saving next_cursor. Continue paging while has_more is true; otherwise stop and keep the cursor for the next poll.

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 in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

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 cursor for the first page. Keep continuation cursors opaque and use them only with the same listing and filters. Events are ordered by sequence ascending. Apply the entire returned page before persisting the next cursor. Each event feed has its own cursor history. Requires a workspace-wide project grant. Project-limited credentials are refused; this feed cannot be filtered to one project.

Defaults when omitted

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • workspace_id (string, optional): Workspace that owns this record.
  • events (array, required).
  • next_cursor (string, required): Opaque checkpoint for this feed. Save it after processing the events, even when has_more is false. Continue paging only while has_more is true.
  • has_more (boolean, required): True when another page is available.
Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Continue

get_workspace Follow the related workflow, inspect capability status, or return to the command index.