Tools
Drops
Three read tools over Drops — scheduled change
windows that apply field values when they open and revert them when they close.
An assistant can answer "what is scheduled to change, and when?" without
touching the schedule itself. All require pim:read.
list_drops_v1
list_drops_v1pim:read
List the account's Drops. Returns the aggregates — use
get_drop_v1 for the per-change detail. No arguments.
get_drop_v1
get_drop_v1pim:readGet one Drop with every change it carries, including each change's apply/revert status and — when it failed — the reason.
| Argument | Type | Description |
|---|---|---|
id | string, required | The Drop id. Must belong to the token's account; cross-account ids return "not found". |
list_master_drops_v1
list_master_drops_v1pim:readList the Drops that will change one item (or its variants), each narrowed to the changes that touch it. The direct way to answer what is scheduled to change on an item, and when, without scanning every Drop.
| Argument | Type | Description |
|---|---|---|
id | string, required | The item id. |
No MCP tool creates, edits, or cancels a Drop; that happens in the app. An assistant drafting edits with the write tools should check list_master_drops_v1 first so it doesn't collide with a change window that is about to open.