Skip to main content
tag_placement_occurrences Attach or remove supplied organizational tags or a subtype on exact retained occurrences. Subtypes require an accepted matching parent. Makes no model request.
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 operation changes saved state. Review its inputs and retry behavior before calling.

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

Attach or remove supplied tags on exact saved occurrences. Organizational tags record customer metadata. A subtype binds to its accepted matching parent decision and saved semantic revision. A changed parent or an evidence concern makes that attachment inapplicable. The whole batch requires the current collection revision. A stale or foreign occurrence refuses the batch without saving attachments.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions. Download input schema · Download output schema

Errors and retries

This write is not annotated idempotent. After a timeout, inspect existing state before repeating it. Operation-specific errors include CLASSIFICATION_PRECONDITION_CHANGED, CLASSIFICATION_METADATA_SCHEMA_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_metadata Follow the related workflow, inspect capability status, or return to the command index.