Export a scoped dataset

Replace the placeholders with values from your own authorized scope before copying this prompt into an MCP client.

Inputs

• {{workspace_id}} Stable workspace ID.
• {{application_id}} Stable application ID.
• {{members}} Exact authorized equality-filter scope.
• {{max_pages}} Maximum typed pages to fetch.
• {{page_size}} Maximum rows per page, from 1 to 50.

Prompt

Use read_v2_program with facts.export.page in {{workspace_id}} / {{application_id}} for members {{members}} and limit {{page_size}}.
For each continuation, pass nextCursor unchanged as cursor and use the same limit. Omit members and snapshotRevision on continuation calls. Fetch at most {{max_pages}} pages.
Preserve the schema, typed literals, full coordinates, sourceRef and each page's contentDigest. Verify snapshotRevision, metadataRevision and securityRevision match across the pages.
Report the exact scope and whether the export is complete or has a continuation. If hasMore is true when the page budget ends, return the nextCursor.
Stop on stale continuation or access error without combining pages from different snapshots.

Example inputs

In the disposable Operating Data Cube, start with the published P01 numeric sample and the P02 supporting-detail sample. Use the filter below, set page_size to 1 and max_pages to 2. Expect an AmountLiteral and a LineDetailLiteral at the same snapshot. Use the returned coordinates to distinguish the periods. Even if a fact changes between requests, a valid continuation still reads its pinned snapshot.

{"Account":"InputA","Entity":"PointA"}

Tools used include list_v2_functions, read_v2_program. See the module guidelines and tool index.