Skip to main content
get_placement_review_history Read dated model suggestions, corrections, undo actions and concerns for one retained physical occurrence. Pages remain bound to that capture and a frozen revision. Missing or expired history does not establish that no earlier changes occurred. Makes no source fetch, write or model call.
Development preview. This command is absent from the verified deployed bundle. Use a matching development 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 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

Reads only retained suggestions, corrections, undo actions and concerns for the exact occurrence and capture. Original classification and later publication dates remain distinct. Pagination freezes a project revision and binds the current credential and evidence. Refresh to include later events. Missing or expired history does not prove that no earlier review occurred. Returns no source passages or provider payloads. Reading neither changes a review nor makes a source fetch or model call.

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.
  • schemaVersion (number, required): must equal 1
  • historyMeaning (string, required): minLength: 1; maxLength: 1000
  • binding (object, required): additional fields rejected
  • asOfRevision (integer, required): minimum: 0; maximum: 9007199254740991
  • readAt (string, required): format: “date-time”; pattern: ”^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z))$”
  • items (array, required): Records in this bounded page. maxItems: 50
  • nextCursor (string / null, required).
  • hasMore (boolean, required).
  • coverage (object, required): Dataset scope and completeness, including limits on what these results establish. additional fields rejected
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. Operation-specific errors include CLASSIFICATION_HISTORY_INVALID_CURSOR, CLASSIFICATION_HISTORY_UNAVAILABLE, CLASSIFICATION_ACCESS_DENIED. 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_placement_context Follow the related workflow, inspect capability status, or return to the command index.