Redo

List the consolidations you participate in, newest packed first.

consolidations

Create a campaign shell. Email requires `subject` and `previewText`. Set the audience and schedule with `updateCampaign`.

create_campaign

Create a customer tag in this store's Redo catalog. The tag's source is Redo Marketing.

create_customer_tag

Start a new return for a customer's order. Accepts an internal order ID, Shopify order ID, or Shopify/display order name such as '#1234'. If an order name does not resolve or you need to disambiguate, call list_orders with providerOrderName, then pass the returned order id here. This creates a draft return that must be configured step-by-step before submission. After creating the draft, use manage_draft_return to configure it, then submit_draft_return to finalize.

create_draft_return

Create a dynamic segment from a condition tree. Attach it to a campaign with updateCampaign.segmentIds.

create_dynamic_segment

Create an inbound shipment fulfilling a purchase order. Its line items are derived from that order, not supplied: when this is the order's only shipment they mirror the order exactly, but once an order has several shipments new order lines are left unassigned and quantity changes stop propagating. Throws a 409 CONFLICT error (with an extension code of PURCHASE_ORDER_NOT_EDITABLE) if the order is closed or cancelled.

create_inbound_shipment

Create a Commerce Agent knowledge article. Defaults to DRAFT so it is not retrievable until you set status to ACTIVE.

create_knowledge_article

Create an automation for a public trigger. Returns the new automation. Date and price-drop triggers are not supported.

create_marketing_automation

Create a new product family.

create_product_family

Add a comment to a return's timeline. If the message follows the format '{product_title} - {variant_title} disposition: {grade}', it will automatically update the matching product's grade (used for 2Boxes-style disposition notes). Use get_return first to verify the return exists and to get product details if writing a disposition note.

create_return_comment

Create an SMS template. `trigger` is required and cannot be UNKNOWN.

create_sms_template

Fetch a single customer by its id (or legacy id), or by email. Provide exactly one.

customer

Fetch a single customer tag by its id. Ids from earlier versions of the Redo API are also accepted.

customer_tag

List customer tags in this store's catalog, optionally filtered by name, provider, or source.

customer_tags

Create or update customer. Create or update a customer profile. Uses the email address as the upsert key — if a customer with that email exists, their profile is updated; otherwise, a new customer is created. ## Profile fields - `firstName` and `lastName` are set directly on the customer. A full display name is automatically generated from these fields. - `phoneNumber` should be in E.164 format (e.g., `+12345678900`). If the number is new, it is added to the customer's contact information. ## Location Providing `location` sets the customer's current location. Only the fields you include are updated. ## Custom fields Use `customFields` to store arbitrary key-value data on the customer (e.g., `pricing_plan`, `subscription_source`). Values can be strings, numbers, or booleans. If a custom field doesn't exist yet, it is created automatically.

customer_upsert

List customers.

customers

Delete a campaign that has not started sending. Returns true if an owned campaign was deleted, false if none matched.

delete_campaign

Delete an email template. Returns true if an owned template was deleted, false if none matched.

delete_email_template

Delete a Commerce Agent knowledge article. Returns true if an owned article was deleted, false if none matched.

delete_knowledge_article

Delete an automation and stop its in-flight runs. Returns true if an owned automation was deleted, false if none matched.

delete_marketing_automation

Delete a product. Returns true if an owned product was deleted, false if none matched. Throws a 409 CONFLICT error (with an extension code of PRODUCT_SOURCE_MANAGED, PRODUCT_HAS_LISTING, or PRODUCT_HAS_INVENTORY) if the product is ineligible for deletion.

delete_product

Delete a product family and all of its products. Returns true if an owned product family was deleted, false if none matched. Throws a 409 CONFLICT error (with an extension code of PRODUCT_SOURCE_MANAGED, PRODUCT_HAS_LISTING, or PRODUCT_HAS_INVENTORY) if the family or any product is ineligible for deletion.

delete_product_family

Delete a product filter on this account. Returns false when the id is missing or belongs to another account. Interactive cart sections on this account that stored the id have that reference cleared.

delete_product_filter

Permanently delete a return tag (matched by name) from the authenticated team's tag library. This also strips the tag from every return that referenced it and from every saved view filter. This action cannot be undone — always confirm with the user before calling.

delete_return_tag

Delete a segment. Returns true if an owned segment was deleted, false if none matched.

delete_segment

Delete an SMS template. Returns true if an owned template was deleted, false if none matched.

delete_sms_template

Delete a webhook endpoint. Returns true if an owned endpoint was deleted, false if none matched.

delete_webhook_endpoint

Fetch a single discount configuration by its id. Ids from earlier versions of the Redo API are also accepted.

discount_code

List discount configurations, optionally filtered by checkout code, platform, group type, or kind.

discount_codes

Update an existing custom analytics report from a full replacement plain-English spec. The tool validates the query before updating the report and waits for the update to finish. It returns status "ready" and a reportUrl. If the request cannot be represented without limitations, the report does not change and the tool requests a revised spec. Missing reports and reports already being prepared return status "error".

edit_custom_analytics_report

Mailboxes the store can use as a campaign From or Reply-To address.

email_addresses

The static email-template variable grammar for a trigger: template variable names, Url keys, context objects, and table collection paths. Does not include this store's discounts, saved sections, or product filters. UNKNOWN returns empty lists.

email_template_variable_catalog

Create a custom analytics report from a plain-English question. This call waits until the report is ready and returns its reportUrl. It validates the query without executing report rows. A proposal with omissions or substitutions returns needs_confirmation. Explain all limitations and obtain merchant approval. Explain that compilation validation does not guarantee runtime success. Then call this tool with the original question and confirmationId to create that exact proposal. An unsupported request returns unavailable without a confirmationId. Ask for a revised request and call again without confirmationId.

generate_custom_analytics_report

Get one Commerce Agent conversation transcript by topic ID. Outbound shopper-agent messages include available provenance such as author, trigger, generation mode, campaign, automation, and human-queue usage. Provenance is intentionally absent for customer, merchant, and older messages when it was not recorded.

get_commerce_agent_conversation

Get the current state of a custom analytics report by id. Use this to poll for status after calling generate_custom_analytics_report. Status "preparing" means the report is still generating, "ready" means it finished successfully (see columns and reportUrl), and "failed" means generation failed (see errorMessage). If the report id does not exist for this team, report is returned as null with an error message.

get_custom_analytics_report

Get detailed customer information, including contact methods, marketing consent, linked accounts, tags, segment memberships, addresses, custom fields, and loyalty details.

get_customer

Get the reusable discount configuration from the shared Discount collection. Use this after campaign, automation, template, or generated-code tools return a discountId and you need the actual offer, code/prefix, provider, expiration, eligibility, usage limits, or stacking rules.

get_discount_config

Get an issued/generated discount code and its usage records. Use this for questions like whether a generated code was used, which customer/order used it, when it expires, what generated it, or what base discount configuration it came from. Provide either generatedDiscountCodeId or discountCode.

get_generated_discount_code

Get detailed information about a specific order including its customer, items, totals, discounts, shipping cost, and taxes. Use list_orders first to find the order ID if you don't have it.

get_order

Get detailed information about a specific return including its items, status, compensation totals, and associated order details. Returns the item IDs needed for process_return. Use list_returns first to find the return ID if you don't have it.

get_return