Tools

Every tool the Operators MCP exposes, grouped by the resource it works on. A tool marked “Requires confirmation” asks you to approve the change in your AI client before it reaches your store.

List tools support pagination (page, per_page max 100), sorting (sort, sort_direction), and date filtering (created_after, created_before, updated_after, updated_before) in YYYY-MM-DD format.

Cycles

list_cycles
get_cycle
update_cycle

List cycles filtered by status, method, dates, and packing status.

Parameter	Values
`status`	`upcoming`, `active`, `complete`, `to_fulfill`, `to_receive`, `to_restock`, `cancelled`
`method_type`	`calendar`, `subscription`, `membership`, `resale`
`packing_status`	`pending`, `printed`, `packed`
`rental_start_from` / `rental_start_to`	Date range for rental start
`customer_email`	Partial match
`item_title`	Partial match

Optionally include related data with include_customer, include_item, include_order, include_line_item.

Get full details of a single cycle by ID.

Parameter	Required	Description
`id`	Yes	Cycle ID (e.g. `SC-1234`)
`include_timeline`	No	`true` to add the 25 most recent timeline events as `timeline`, with a `total_count`. Use `list_timeline_events` for the full history

Returns the complete cycle record with customer, item, order, charges, and return data.

Update a cycle’s packing status, dates, or item assignment. Requires confirmation.

Parameter	Description
`id`	Cycle ID (required)
`packing_status`	`pending`, `printed`, `packed`
`item_id`	Item ID to assign
`rental_start` / `rental_end`	Reschedule dates (`YYYY-MM-DD`)
`fulfilled_at` / `received_at`	Mark as fulfilled or received (`YYYY-MM-DD`)
`prepare_from` / `restock_by`	Override the preparation start or restock end date (`YYYY-MM-DD`). Pass `null` to revert to the automatic date computed from the shop’s logistics buffers.

Outbound fulfillments

Outbound fulfillments are the packing queue: each one groups the cycles going out to a customer together, so one update moves every cycle traveling together.

list_outbound_fulfillments
get_outbound_fulfillment
update_outbound_fulfillment

List the outbound fulfillment queue with status and date filters.

Parameter	Values
`status`	`pending` (not yet fulfilled), `due` (fulfill by today or unscheduled), `overdue`, `scheduled` (fulfill date in the future), `fulfilled`
`delivery_method_type`	`shipping`, `pick_up`
`customer_email`	Partial match
`fulfill_by_after` / `fulfill_by_before`	Fulfill-by date range (`YYYY-MM-DD`)

Sortable by created_at, fulfill_by, or arrive_by. Each fulfillment carries its schedule dates, customer, and the cycles going out together with their packing statuses.

Get full details of a single outbound fulfillment.

Parameter	Required	Description
`id`	Yes	Outbound fulfillment ID (numeric)

Returns schedule dates, status, delivery method, customer, order, and the cycles going out together with their items, packing statuses, pick locations, and serials.

Update an outbound fulfillment’s schedule dates or mark it fulfilled. Requires confirmation.

Parameter	Description
`id`	Outbound fulfillment ID (required)
`arrive_by`	Date the items should reach the customer (`YYYY-MM-DD`)
`fulfill_by`	Date the items must be sent out (`YYYY-MM-DD`)
`prepare_from`	Override the computed preparation start date (`YYYY-MM-DD`)
`expected_arrival`	Expected arrival date of a sent fulfillment (`YYYY-MM-DD`)
`fulfilled_at`	When the items were sent (`YYYY-MM-DD`, ISO 8601, or `now`). Setting this marks the fulfillment complete
`pin_dates`	Date fields to hold in place while others recompute: `arrive_by`, `fulfill_by`, `prepare_from`

Moving a boundary date recomputes the dependent dates unless they’re pinned. Pass clear as any date value to null it and let it recompute. clear on fulfilled_at marks the fulfillment as not fulfilled after all.

Inbound receivals

Inbound receivals are the receiving queue: each one groups the cycles coming back from a customer together.

list_inbound_receivals
get_inbound_receival
update_inbound_receival

List the inbound receival queue with status and date filters.

Parameter	Values
`status`	`pending` (not yet received), `due` (receive by today or unscheduled), `overdue`, `scheduled` (receive date in the future), `received`
`return_method_type`	`shipping`, `drop_off`
`customer_email`	Partial match
`receive_by_after` / `receive_by_before`	Receive-by date range (`YYYY-MM-DD`)

Sortable by created_at, receive_by, or return_by. Each receival carries its schedule dates, customer, and the cycles coming back together.

Get full details of a single inbound receival.

Parameter	Required	Description
`id`	Yes	Inbound receival ID (numeric)

Returns schedule dates, status, return method, customer, order, and the cycles coming back together with their items.

Update an inbound receival’s schedule dates or mark it received. Requires confirmation.

Parameter	Description
`id`	Inbound receival ID (required)
`return_by`	Date the customer must send or hand the items back (`YYYY-MM-DD`)
`receive_by`	Date the items should be back with the store (`YYYY-MM-DD`)
`restock_by`	Override the computed restock date (`YYYY-MM-DD`)
`expected_return`	Expected return date of items already on their way back (`YYYY-MM-DD`)
`received_at`	When the items were received back (`YYYY-MM-DD`, ISO 8601, or `now`). Setting this marks the receival complete
`pin_dates`	Date fields to hold in place while others recompute: `return_by`, `receive_by`, `restock_by`

Moving a boundary date recomputes the dependent dates unless they’re pinned. Pass clear as any date value to null it and let it recompute. clear on received_at marks the receival as not received after all.

Inventory

list_items
get_item
update_item

List inventory items filtered by visibility, status, condition, and availability.

Parameter	Values
`visibility`	`available`, `unavailable`, `sold`, `retired`, `expected`. Also accepts the admin labels Active and Draft
`processing_status`	`unprocessed`, `processed`
`available`	`true` (not rented), `false` (out on a cycle)
`product_title`	Partial match
`sku`	Partial match
`condition_id`	Filter by condition

An unrecognized visibility value returns an Invalid visibility error rather than the unfiltered list.Returns item ID, product/variant title, SKU, serial, visibility, condition, and pick location.

Get full details of a single inventory item by ID.

Parameter	Required	Description
`id`	Yes	Item ID (e.g. `#1042`)

Returns the complete item record with serial, SKU, condition, visibility, processing status, pick location, tags, custom fields, acquisition cost and lifecycle revenue, the current and upcoming cycles, and blocked dates. Blocked dates include blocks inherited from the item’s variant, product, or the whole store. Cycle bookings are not included.

Update an item’s condition, serial, pick location, or visibility. Requires confirmation.

Parameter	Description
`id`	Item ID (required)
`condition_id`	Condition ID to assign
`serial`	Serial number, unique per store
`pick_location`	Free-text pick location (e.g. `Shelf B3`)
`visibility`	`available`, `unavailable`, `sold`, `retired`, `expected`. Also accepts the admin labels Active and Draft

Pass clear as the value for condition_id, serial, or pick_location to remove it.Visibility is the item’s fleet state, matching the Visibility card in the admin:

Value	Admin label	Meaning
`available`	Active	In circulation and can be rented or sold
`unavailable`	Draft	Out of circulation for now
`sold`	Sold	Sold to a customer
`retired`	Retired	No longer suitable for rental or resale
`expected`	Expected	On its way in, such as a trade-in that hasn’t arrived yet

Values are case-insensitive, so Sold and sold both work. Anything else returns an Invalid visibility error.

Products

list_products
get_product

List catalog products filtered by title, status, and enabled cycle methods.

Parameter	Values
`title`	Partial match
`status`	`active`, `archived`, `draft`, `unlisted`
`method_type`	Only products with this method enabled: `subscription`, `membership`, `calendar`, `resale`, `trade_in`

Sortable by created_at or title. Returns per-product method flags plus variant and item counts.

Get full details of a single product.

Parameter	Required	Description
`id`	Yes	Shopify product ID, internal ID, handle, or exact title

Returns status, vendor, tags, per-method configuration with option counts, variants with their inventory counts, inventory totals, and cycle activity counts. Products backed by a membership plan, bundle, card authorization, or deposit are classified by kind and returned without inventory.

Customers

list_customers
get_customer

List customers filtered by activity, value, and balance.

Parameter	Description
`customer_email`	Partial match
`name`	Partial match
`has_active_rentals`	`true` or `false`
`lifetime_value_min_cents`	Minimum lifetime value
`outstanding_balance_min_cents`	Minimum outstanding balance

Sortable by lifetime_value_cents, rentals_count, outstanding_balance_cents.

Get full details of a single customer.

Parameter	Required	Description
`id`	Yes	Customer email, Shopify customer ID, or internal ID
`include_timeline`	No	`true` to add the 25 most recent timeline events as `timeline`, with a `total_count`. Use `list_timeline_events` for the full history

Returns contact info and default address, lifetime value, outstanding and deposit balances, cycle counts, membership status, identity verification status, and tags. The timeline covers membership changes, billing failures, identity verification, and staff notes.

Returns

list_returns
get_return
create_return
update_return

List returns filtered by status, receival, and credit status.

Parameter	Values
`status`	`requested`, `expected`, `received`, `in_progress`, `completed`, `cancelled`
`receival_status`	`unreceived`, `partially_received`, `received`
`credit_status`	`uncredited`, `partially_recredited`, `recredited`
`incomplete`	`true` to show only incomplete returns
`customer_email`	Partial match

Optionally include related data with include_customer, include_return_lines.

Get full details of a single return by ID.

Parameter	Required	Description
`id`	Yes	Return ID (e.g. `#2001`)
`include_timeline`	No	`true` to add the 25 most recent timeline events as `timeline`, with a `total_count`. Use `list_timeline_events` for the full history

Returns the complete return record with customer, return lines, conditions, return method, and tags. The timeline covers approvals, receivals, credits, and emails.

Create a return order for a customer. Requires confirmation.

Parameter	Required	Description
`customer_id`	Yes	Customer email or Shopify ID
`rental_ids`	Yes	Array of rental IDs (e.g. `['SC-1042', 'SC-1043']`)
`return_method_type`	No	`collection` or `return_label`

Update a return order’s status or return line statuses. Requires confirmation.

Parameter	Description
`id`	Return ID (required)
`status`	`requested`, `expected`, `received`, `in_progress`, `completed`, `cancelled`
`return_lines`	Array of `{ id, status }` where status is `awaiting`, `received`, or `missing`

Charges

list_charges
get_charge

List charges with optional status filtering.

Parameter	Description
`status`	`paid`, `unpaid`, `cancelled` (default: all)
`customer_email`	Partial match
`amount_min_cents` / `amount_max_cents`	Filter by amount
`category_type`	`Checkout`, `Generic`, `BillingCycle`

Optionally include related data with include_customer, include_dunning.

Get full details of a single charge by ID.

Parameter	Required	Description
`id`	Yes	Charge ID (e.g. `#3001`)
`include_timeline`	No	`true` to add the 25 most recent timeline events as `timeline`, with a `total_count`. Use `list_timeline_events` for the full history

Returns the charge with amounts paid and due, each payment attempt with its line breakdown and order, the linked cycle or membership, and the payment collector’s retry state. The timeline covers creation, billing attempts, and payment.

Pricing

list_method_options

List pricing options for a given method, filtered by product and price range.

Parameter	Required	Description
`method_type`	Yes	`subscription`, `membership`, `calendar`, `resale`
`product_id`	No	Filter by product
`price_min_cents` / `price_max_cents`	No	Filter by price

Returns method-specific fields, for example the recurring price and billing interval for subscriptions, or the duration for calendar.

Availability

check_availability
list_blocked_dates
create_blocked_date
delete_blocked_date

Check whether a product or variant can be booked for a date range, accounting for the preparation, delivery, return, and restock time from your logistics buffers around both the proposed booking and existing reservations.

Parameter	Required	Description
`variant_id` / `sku` / `product_id` / `product_title`	One of	Which variants to check. SKU and product title support partial matches, and product lookups check all variants
`start_date`	Yes	The day the customer receives the item (`YYYY-MM-DD`)
`end_date`	No	The day the customer hands the item back (`YYYY-MM-DD`). Omit for an open-ended booking (e.g. a subscription), which conflicts with any future block
`delivery_method_type`	No	`shipping` or `pick_up` (default: the shop default)
`return_method_type`	No	`shipping` or `drop_off` (default: the shop default)

Returns, per variant: a bookable verdict with item counts, the contiguous available windows around the requested dates, and per-item conflicts showing each block’s padded date range and the cycle causing it. When transit time is the only blocker, an alternative verdict for pick-up delivery with drop-off return is included. Checks up to 10 matching variants.

List blocked date ranges, optionally scoped to a resource or filtered to a date window. Cycle bookings are not included.

Parameter	Description
`resource_type`	Only include blocks on this resource type: `item`, `variant`, `product`, or `shop`
`resource_id`	Resource ID to scope to. Required with `resource_type` except for `shop`
`from` / `to`	Only include blocks overlapping this date window (`YYYY-MM-DD`)

Sortable by created_at or from. Dates are day-bounded in the shop time zone. Each result includes its ID, which delete_blocked_date takes.

Block an item, variant, or product from being booked over a date range. Requires confirmation.

Parameter	Required	Description
`resource_type`	Yes	`item`, `variant`, or `product`
`resource_id`	Yes	Formatted or numeric ID for items, Shopify ID or numeric ID for variants and products
`from`	No	First blocked date (`YYYY-MM-DD`, inclusive). Omit for open-ended start.
`to`	No	Last blocked date (`YYYY-MM-DD`, inclusive). Omit for open-ended end.
`description`	No	Optional note (e.g. `Repairs`, `Reserved for photoshoot`)

At least one of from or to must be provided. Dates are day-bounded in the shop time zone.

Delete a blocked date range so the resource can be booked again. Requires confirmation.

Parameter	Required	Description
`id`	Yes	Blocked date ID, as returned by `list_blocked_dates` or `create_blocked_date`

Deleting can’t be undone. Recreate the block with create_blocked_date if you need it back. Cycle bookings can’t be deleted this way.

Parameter	Required	Description
`resource_type`	Yes	`cycle`, `item`, or `return`
`resource_id`	Yes	Resource ID (e.g. `#1042`)

Parameter	Required	Description
`resource_type`	Yes	`cycle`, `item`, or `return`
`resource_id`	Yes	Resource ID (e.g. `#1042`)
`tag`	Yes	Tag title to add

Parameter	Required	Description
`resource_type`	Yes	`cycle`, `item`, or `return`
`resource_id`	Yes	Resource ID (e.g. `#1042`)
`tag`	Yes	Tag title to remove

Comments

list_comments
add_comment

List the comments and notes on a cycle, item, customer, or return, newest first.

Parameter	Required	Description
`resource_type`	Yes	`cycle`, `item`, `customer`, or `return`
`resource_id`	Yes	Resource ID or email for customers

Each comment includes its message, author, and timestamp. Comments are one kind of timeline event, so for the system events around them, such as emails, approvals, and billing, use list_timeline_events.

Add a comment or note to a cycle, item, customer, or return. Requires confirmation.

Parameter	Required	Description
`resource_type`	Yes	`cycle`, `item`, `customer`, or `return`
`resource_id`	Yes	Resource ID or email for customers
`body`	Yes	Comment text

Timeline

The timeline is the same event history the admin shows on the cycle, customer, item, and charge pages: status changes, automated emails, credits, billing attempts, approvals, and staff comments. Events on a related record appear too, so a customer’s timeline includes their memberships and payment collector, and a cycle’s timeline includes its charges.

list_timeline_events

List the event history of a cycle, return, customer, item, or charge, newest first.

Parameter	Required	Description
`resource_type`	Yes	`cycle`, `return`, `customer`, `item`, or `charge`
`resource_id`	Yes	Resource ID (e.g. `SC-1234` or `#2001`), or email for customers
`event_type`	No	`basic` for system events or `comment` for staff comments. Omit for both
`action`	No	Only basic events with this action, for example `created`, `cancelled`, `approved`, `failed`, `paid`, or `recredited`
`created_after` / `created_before`	No	Only events in this date range (`YYYY-MM-DD`)
`sort_direction`	No	`desc` (default, newest first) or `asc`
`page` / `per_page`	No	Pagination, 25 per page by default and 100 at most

Each event carries its type, created_at, a plain-text message with any formatting stripped, the author who caused it, and the action and arguments of a system event. A subject identifies the record the event is about when it isn’t the resource itself, such as the charge or billing_attempt behind a failed payment on a customer’s timeline.

Overview

Use cases

MCPs

Shopify

Cycles

Outbound fulfillments

Inbound receivals

Inventory

Products

Customers

Returns

Charges

Pricing

Availability

Tags

Comments

Timeline

​Cycles

​Outbound fulfillments

​Inbound receivals

​Inventory

​Products

​Customers

​Returns

​Charges

​Pricing

​Availability

​Tags

​Comments

​Timeline

Cycles

Outbound fulfillments

Inbound receivals

Inventory

Products

Customers

Returns

Charges

Pricing

Availability

Tags

Comments

Timeline