Redo

Resolve linked configuration for a specific automation step. Use this after get_automation when a step has an opaque template/config ID. Resolves Recover steps into scenarios, fallback messaging, agent/brand settings, and discount ID; email steps into subject, preview, and builder sections; and SMS steps into message content, prefix, AI config, and attachments.

get_automation_step_configuration

Return automation-level rollups plus per-step performance for a metric family. Use metricType='recover_conversation' and stepTypes=['recover'] for Recover automation performance questions like recovered revenue, reply rate, conversion rate, or which Recover step is performing better.

get_automation_step_performance

Get detailed information about a specific marketing campaign, including its templates (email subject lines or SMS content variants), audiences (customer groups), status, and schedule. Use list_campaigns first to find the campaign ID if you don't have it.

get_campaign

Return per-campaign performance metrics plus overall totals (with a comparison to the prior period of equal length) for a given date range. Metrics include revenue, spend, ROI (as a percentage), revenue per recipient, and counts of orders / clicks / opens / sends. Currency values are plain numbers in the store's currency. Use `campaignId` to filter rows to a single campaign; totals remain period-level.

get_campaign_performance

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

Get detailed configuration for a marketing segment/audience, including counts and the dynamic condition tree when applicable. Use this after list_segments or after get_campaign returns included/excluded audience IDs.

get_segment

Get an email or SMS marketing template by ID. Use this to inspect subject lines, email builder sections, SMS content, prefix content, attachments, and AI config when a campaign or automation references a template ID.

get_template

List automations for the merchant's team. Returns automation IDs, names, enabled state, category/schema, step count, and unique step types. Use the stepTypes filter to discover automations for a feature, such as ['recover'], then call get_automation for the full step configuration.

list_automations

List marketing campaigns for the merchant's team. Filter by channel (email/sms), status, name substring, or scheduled-date range. Returns a summary for each campaign (id, name, channel, status, scheduledAt, sentAt, variant counts, audience counts). Use get_campaign with a specific campaign ID for full details, or get_campaign_performance for per-campaign metrics.

list_campaigns

List the merchant's custom analytics reports, most recent first. Use search to filter by title or requested question. Each report includes its id, status (preparing, ready, or failed), and columns once ready. Use get_custom_analytics_report with a report's id for its full details and reportUrl.

list_custom_analytics_reports

Search and list customer records for the merchant. Use this to find customer IDs before calling get_customer, or to answer questions about customers by name, email, phone, or segment membership.

list_customers

Search and list orders, sorted by most recent first. Filter by order name, customer email, or date range. Returns summary information for each order; use get_order with a specific order ID for full details. Supports pagination via the pageNext cursor in the response.

list_orders

List every return tag defined for the authenticated team. Use this to resolve the exact stored name (case-sensitive) before calling `upsert_return_tag` or `delete_return_tag` when the user refers to a tag loosely.

list_return_tags

Search and list returns, sorted by most recent first. This is the starting point for finding returns — filter by order name, customer email, status, or date range. Returns summary information for each return; use get_return with a specific return ID for full details. Supports pagination via the pageNext cursor in the response.

list_returns

List marketing segments/audiences for the merchant's team. Use this to discover segment IDs before calling get_segment, or to inspect the audiences included/excluded on a campaign.

list_segments

Configure a draft return step-by-step. This tool acts as a state machine — it only accepts actions valid for the current step and advances the flow automatically. Each response tells you the current step, available actions, and relevant data. Steps proceed in order: select items → walk return flow (reason/questions per item) → choose compensation → set merchant overrides → choose shipment method → configure exchange (if applicable). Use go_back to return to a previous step. The response always includes availableActions telling you exactly what you can do next.

manage_draft_return

Process a return's products by accepting or rejecting each one. Before calling this tool, you MUST: (1) call get_return to retrieve the return's items and their IDs, (2) check that items are in an 'open' status — if items show as 'rejected' or 'complete' on an open return, the return is in an inconsistent state; explain this to the merchant and ask if they want you to re-process the items (accept them) or close the return instead, (3) confirm with the user which products to process and whether each should be accepted or rejected, (4) for accepted products, ask whether to restock. Grade is optional and does not need to be asked unless the user mentions it, and (5) if rejecting any products, ask the user if they'd like to include a message to the customer explaining the rejection. Each product in the request needs either reject:true OR a processInput object, not both. For customerNotes: ONLY include the user's exact words if they provide a message. NEVER generate or fabricate customerNotes — omit the field if the user declines or doesn't provide one. NEVER set newMerchantAdjustment unless the user explicitly requests a specific refund amount for that item — omit the field entirely for a normal full refund. Setting newMerchantAdjustment to 0 will issue a $0 refund to the customer.

process_return

Reopen a return that was previously completed or rejected. This resets all processed/rejected items back to open, clears pending processing info, resets the expiration date, and marks the return as reopened. Important: reopening does NOT reverse any refunds, exchanges, or other actions performed during processing. The team must have the 'Allow reopen after processing' setting enabled for processed returns. Confirm with the user before reopening.

reopen_return

Submit a fully configured draft return to create the actual return. Only succeeds when all required steps are complete (currentStep must be 'ready'). Call this after configuring the draft return via manage_draft_return. Returns the created return ID.

submit_draft_return

Update the status of a return. Valid statuses: in_transit, delivered, needs_review, in_review, flagged, pre-shipment. For reopening a return (setting to open), use the reopen_return tool instead. For closing a return (setting to complete), use the close_return tool instead. Confirm the desired status with the user before calling this tool.

update_return_status

Create, update, or rename a return tag for the authenticated team. If no tag with `name` exists, a new one is created. If a tag with `name` exists and `newName` is omitted, only its pillTheme is updated. If a tag with `name` exists and `newName` is provided, the tag is renamed to `newName` and cascaded to every return that referenced it and every saved view filter. Confirm with the user before creating a new tag or renaming one.

upsert_return_tag