MCP App Store
by KeenEthics
Scanio icon

Scanio MCP Server for Claude and ChatGPT

By Elchunen Chaim Freund

Overview

Scanio is an operations workspace for brands that sell to online retailers as first-party (1P) vendors, and for their teams. It tracks each product's availability and price on the retailer's site, vendor sales and traffic, purchase orders, listing changes, product content and search terms. Connect your Scanio account to ask about all of it in plain language and to get the work done: create, assign, update and complete tasks; add and edit products, tags and product groups; fill in and confirm missing product data and request it from your suppliers by email; work through standard operating procedure (SOP) checklists and task workflows; and handle the Change Inbox, bundles, saved views and notifications. Through the connection, Scanio emails only your teammates, your saved contacts and people Scanio has already emailed in that conversation. Every email it writes for you is shown to you in full before it is sent, except the automatic data requests your account has switched on, which go out as set up in Scanio. Apart from Scanio's usual notifications to your teammates, a connection sends at most 30 emails in any 24 hours. The connection reaches only the one Scanio account you connect, with the same permissions you have in Scanio, and tasks, tags and notifications show what was done through it. Requires a Scanio account. Connecting asks you to confirm that model training is off for the AI account you connect, because the retail data in Scanio may not be used to train AI models.

How to connect

  1. Claude: Open the Scanio listing in the Claude connectors directory and choose Connect. Claude listing Scanio exposes 112 tools here.
  2. ChatGPT: Open the Scanio listing in the ChatGPT app directory and choose Connect. ChatGPT listing Scanio exposes 115 tools here.

Tools

add_products

ChatGPT
Use this when the user asks Scanio to start tracking new products by ASIN. Adds up to 50 products, with any details given (sku, title, brand, upc, category, subcategory, comment, notes, or a vendor_code with its cost). With from_amazon_reports, only ASINs the account's vendor reports or purchase orders already know are added, with the title and brand from those reports; the rest are listed in not_known_to_amazon. An ASIN already tracked is left as it is and listed in already_tracked, so repeating a call adds nothing. Each new product starts tracking the account's default data points (Missing Data), and in an account Scanio has never checked, the first products added start its first daily check of their product pages. If the account has automatic data requests switched on in Settings, each new product also emails a data request, in the connected user's name, to the people responsible for its data points. Those emails go only if this connection has permission to send email, cannot be recalled, and count toward the 30 emails this connection may send in 24 hours. data_request_emails is how many left Scanio; data_request_emails_held is how many were held because email sending is switched off for the account; and data_request_note says why any were not sent: email is not set up on this Scanio server, the connection has no permission to send email (the user can send them from Scanio), the daily limit, or a failure partway, after which the rest of that batch is not sent either (for example "1 data request sent, 2 not sent: <reason>"). With permission to send email, each new product counts as at least one email, checked before anything is added. Nobody else is notified. If Scanio stops partway, stopped says why and not_added lists what was not added. To change products already tracked use update_products.

add_products_to_group

ChatGPT
Use this when the user asks to put products into a product group. Adds up to 50 products, each tracked by the account, to the group named by group, or changes nothing if one is not. The answer lists the products added and those already in the group, so repeating a call changes nothing more. Nobody is notified. To take products out use remove_products_from_group; to make a new group use create_product_group.

add_tags_to_products

ChatGPT
Use this when the user asks to tag products, for example to tag five products "Needs content". Puts each named tag on up to 50 of the account's products, the same change as the tag editor in Scanio, recorded in the tag history under the connected user and marked as made through this connector. The tags must already exist (list_tags lists them; create_tag makes one) and every product must be tracked by the account, or nothing is changed. The answer lists, for each tag, the products tagged and those that already had it, so repeating a call changes nothing more. Nobody is notified. To tag every product in a group use apply_tag_to_group; to take tags off use remove_tags_from_products.

add_task_comment

ChatGPT
Use this when the user asks to add a note, an update or a piece of text to a task that exists, for example to post proposed listing copy on the task about that product. Adds a comment to the task, named by its task number, and can attach text the user provided or asked for as a .txt or .md file. The task's assignee, creator and watchers, other than the connected user, are notified in the app and by email with the start of the comment (their notification settings apply), and the email cannot be recalled. Each call posts another comment, so repeating it posts the comment again. To change the task itself use update_tasks.

add_workflow_step

ChatGPT
Use this when the user asks to add a step to a task's workflow, for example a step to request a certificate from a supplier. Adds the step at the end of the workflow of the task named by its task number, with a label and, optionally, one responsible party (contact_email or user_email, not both) and an email_template. Each call adds another step. To change a step use edit_workflow_step; to start from a whole template use apply_workflow_template. Done as the connected user and recorded in the task's history as done through this connector; nobody is notified in the app. This tool never sends a step's request email (send_workflow_step_email does).

apply_tag_to_group

ChatGPT
Use this when the user asks to tag every product in a product group. Puts the tag on each product in the group now; products added to the group later are not tagged. No tag history entry is written per product. Repeating a call changes nothing more. Nobody is notified. For particular products use add_tags_to_products. unlink_tag_from_group removes only the record that the tag was applied to the group, never the products' tags.

apply_workflow_template

ChatGPT
Use this when the user asks to give a task the steps of a workflow template, for example the standard new supplier onboarding steps. Sets up the steps of the task named by its task number from the template named by template (the account's own template is used when it has the same name as a built-in one; an unknown name is answered with the templates there are). Only on a task with no steps yet, so a task that has steps is refused; change its steps with add_workflow_step and edit_workflow_step. If the account has automatic data requests switched on in Settings, this also emails a data request, in the connected user's name, to the person responsible for each of the task's open Missing Data cells; the template is applied either way. Those emails go only if this connection has permission to send email, cannot be recalled, and count toward the 30 emails this connection may send in 24 hours. data_request_emails is how many left Scanio; data_request_emails_held is how many were held because email sending is switched off for the account; and data_request_note says why any were not sent: email is not set up on this Scanio server, the connection has no permission to send email (the user can send them from Scanio), the daily limit, or a failure partway, after which the rest of that batch is not sent either (for example "1 data request sent, 2 not sent: <reason>"). Needs the account's workflow templates turned on. Done as the connected user and recorded in the task's history as done through this connector; nobody is notified in the app. This tool never sends a step's request email (send_workflow_step_email does).

approve_procedure_checklists

ChatGPT
Use this when a manager approves procedure checklists that were handed in early and are waiting for approval (list_procedures_awaiting_approval lists them). Approves each one, and each submitter is notified in the app, which cannot be undone. Takes up to 50 checklists, each named by procedure, person (the submitter's email) and period. Nobody may decide on their own checklist. If any named checklist is not waiting for approval, nothing is changed, so repeating a call changes nothing. If Scanio refuses one partway, the call stops: results lists the decisions made, which must not be sent again, failed the one refused and why, and not_attempted the rest, each named by procedure, person and period. Procedures are a feature Scanio turns on per account; where it is off, every call says so and does nothing. To turn checklists down use reject_procedure_checklists.

archive_contact

ChatGPT
Use this when the user says a contact should no longer be used, for example someone who left the supplier. Archives the contact, named by its name or email: it is kept, and cells and workflow steps that name it keep it, but it can no longer be emailed. There is no unarchive; adding the person again with create_contact creates a new contact. An archived contact is not found again, so repeating a call changes nothing more. Needs the Contacts feature on for the account. Nobody is notified and no email is sent.

assign_missing_data

ChatGPT
Use this when the user wants to change who is responsible for missing data: its owner (a team member) or its supplier (a contact). Sets owner_email, supplier or both on each cell; null hands that role back to the data point's default, and a role not given keeps its value. A cell that already has what is asked is reported unchanged. Takes up to 50 cells, each a product (ASIN, or SKU when it has no ASIN) and a data point, each once; every cell must already be tracked (start_tracking_missing_data adds one), and the Missing Data feature must be on for the account. Every cell is checked before anything changes, and a refusal names each bad cell. Nobody is notified and no email is sent. The change is copied to the account's linked Google Sheet, as it is when made in Scanio. If Scanio refuses a change partway, the call stops and the answer lists what changed (updated), what failed and what was not tried. To change a data point's defaults for all its cells use set_data_point_defaults. Repeating a call changes nothing more.

attach_file_to_missing_data

ChatGPT
Use this when the user wants to keep a piece of text with missing data as a file, for example a specification or notes they provided or asked you to write. Attaches a text file (text/plain or text/markdown) to each cell. The file is stored in Scanio only: it is not emailed, not written to the Google Sheet, and the cell's state does not change. Each call attaches the file again. Takes up to 50 cells, each a product (ASIN, or SKU when it has no ASIN) and a data point, each once; every cell must already be tracked (start_tracking_missing_data adds one), and the Missing Data feature must be on for the account. Every cell is checked before anything changes, and a refusal names each bad cell. Nobody is notified and no email is sent. If Scanio refuses a change partway, the call stops and the answer lists what changed (updated), what failed and what was not tried.

clear_missing_data_in_progress

ChatGPT
Use this when the user says work on some products' missing data has stopped. Removes the in-progress flag from each product's cells and changes nothing else: no owner, value or cell is removed. Takes products only (ASIN, or SKU when it has no ASIN), up to 50. Needs the Missing Data feature on for the account. Nobody is notified and no email is sent. Repeating a call changes nothing more. To set the flag use mark_missing_data_in_progress.

clear_missing_data_value

ChatGPT
Use this when the user says a filled value is wrong or must be gathered again. Clears the value of each filled cell, which goes back to open; the cleared value stays in the cell's history. The cell must be filled. Takes up to 50 cells, each a product (ASIN, or SKU when it has no ASIN) and a data point, each once; every cell must already be tracked (start_tracking_missing_data adds one), and the Missing Data feature must be on for the account. Every cell is checked before anything changes, and a refusal names each bad cell. Nobody is notified and no email is sent. The change is copied to the account's linked Google Sheet, as it is when made in Scanio. If Scanio refuses a change partway, the call stops and the answer lists what changed (updated), what failed and what was not tried. To set a different value directly use fill_missing_data. Repeating a call changes nothing more.

clone_workflow_template

ChatGPT
Use this when the user wants to start a new workflow template from an existing one, for example to adjust one of Scanio's built-in templates. Copies the template named by template (built in, or one of the account's own) as "<name> (custom)", which edit_workflow_template can then change. Template names are unique in an account, so a second copy of the same template is refused and changes nothing. Nobody is notified. Workflows are a feature Scanio turns on per account; where they are off, every call says so and does nothing.

compare_products_between_periods

ChatGPT
Use this when the user asks how particular products did in one period compared with another, for example this quarter against the same quarter last year. Compares up to 50 ASINs between the current range and an earlier one: the same length of time just before (comparison_mode prior_period, the default), the same dates a year earlier (yoy), or prior_start to prior_end (custom); neither range may exceed 12 months. metrics chooses the figures, by default sales.ordered_revenue, traffic.glance_views and pos.ordered_units. Each row has asin, title, vendor_sku, sparse (too little data to compare well), values (per metric: current, prior, change, pct_change, and big_drop for a fall of 50% or more) and merged (a product merge's label and members, or null; dollar figures add up across members, unit counts do not). include_periods adds each figure by week, or by month with granularity monthly. A figure only the manufacturing view reports (sales.ordered_revenue, sales.ordered_units, traffic.glance_views) comes back null with not_reported true when nothing reported it. For the biggest movers across every product use get_top_gaining_and_declining_products.

confirm_bundle_suggestions

ChatGPT
Use this when the user accepts bundles Scanio suggested (list_bundles with include_suggestions shows them). Creates up to 50 bundles, each named by the suggestion's bundle_asin, with the component ASINs the user chose and an optional label. Each must be a current suggestion, or the call is refused and nothing is created; the answer lists the bundles created and those already bundled. A product that is part of a product merge (list_product_merges) cannot be in a bundle. ASINs the account does not track are linked as they are; with track_missing_products they are also added as products, whose product pages Scanio then checks every day like the others. No one is notified. For a bundle that is not a suggestion use create_bundle.

confirm_product_merge_suggestion

ChatGPT
Use this when the user accepts a merge Scanio suggested (list_product_merges with suggestions "pending" shows them). A product merge joins an old listing and its replacement, for example a single pack and its case pack, so Scanio reads them as one product: dollar figures add up across members, unit counts stay per member. Merges the suggestion's old listing (from_asin) and its replacement (to_asin) and marks the suggestion confirmed; the replacement is the primary unless primary_asin says otherwise, and a label and pack labels can be set. A pair that is not a pending suggestion, or an ASIN already in a merge, is refused, so repeating a call is refused. Members the account does not track are merged as they are; with track_missing_products they are also added as products, whose product pages Scanio then checks every day. No one is notified. Merges cannot be undone with these tools. To merge listings Scanio did not suggest use create_product_merge.

confirm_proposed_missing_data

ChatGPT
Use this when the user accepts a value a supplier proposed, in an email reply or in the linked Google Sheet, for cells waiting for confirmation (status awaiting_confirmation in list_missing_items). Each cell becomes filled with the proposed value, or with value when the user corrects it. Takes up to 50 cells, each a product (ASIN, or SKU when it has no ASIN) and a data point, each once; every cell must already be tracked (start_tracking_missing_data adds one), and the Missing Data feature must be on for the account. Every cell is checked before anything changes, and a refusal names each bad cell. Nobody is notified and no email is sent. The change is copied to the account's linked Google Sheet, as it is when made in Scanio, and a corrected value to the account's own source sheet when the account has chosen that. If Scanio refuses a change partway, the call stops and the answer lists what changed (updated), what failed and what was not tried. To turn a proposal down use reject_proposed_missing_data. Repeating a call changes nothing more.

confirm_workflow_step

ChatGPT
Use this when the user says a step of a task's workflow is done, for example the supplier sent what was requested. Marks the step confirmed, named by its number on the task named by its task number (step numbers are the ones get_task's workflow_steps and Scanio's Workflow tab show), with optional notes. It also fills that step's Missing Data cell (with the notes, or "Confirmed"), and the filled cell reaches the account's linked Google Sheet at the next sheet sync. A step already confirmed is answered as unchanged. Done as the connected user and recorded in the task's history as done through this connector; nobody is notified in the app. This tool never sends a step's request email (send_workflow_step_email does).

create_bundle

ChatGPT
Use this when the user asks to link a bundle listing to the products it contains, so Scanio shows them as one combined row. Creates one bundle from component_asins with a bundle_asin, a label, or both. A second bundle for the same bundle_asin is refused; without a bundle_asin, repeating the call creates a duplicate bundle. A product that is part of a product merge (list_product_merges) cannot be in a bundle. ASINs the account does not track are linked as they are; with track_missing_products they are also added as products, whose product pages Scanio then checks every day like the others. No one is notified. Bundles cannot be deleted with these tools. To change a bundle use edit_bundle; to accept Scanio's suggestions use confirm_bundle_suggestions.

create_contact

ChatGPT
Use this when the user wants to save an outside person, usually someone at a supplier, so Scanio can email them or make them responsible for missing data or a workflow step. Creates a contact with a name and, optionally, email, organization, role, phone and notes. An email address another contact already has is refused and that contact is named, so repeating a call creates nothing more. Needs the Contacts feature on for the account. Nobody is notified and no email is sent. To change a contact use edit_contact.

create_custom_columns

ChatGPT
Use this when the user asks to add extra columns to their products in Scanio, for example a "Launch date" column. Creates up to 50 custom columns, each with a name and a data_type. A name or key that already exists is refused, so nothing is overwritten and repeating the call creates nothing new. No one is notified. Columns cannot be deleted with these tools. To rename a column or change its type use edit_custom_column; to change their order use reorder_custom_columns.

create_data_point

ChatGPT
Use this when the user wants Scanio to collect a new piece of product information, for example a new "Case pack dimensions" column. Creates a data point: kind column (the default) adds a column with a cell for every product, and per_product tracks it only for the products it is added to; added_to_new_products makes every product added later track it; default_owner_email and default_supplier are who its cells fall back to. A name already in use, a built-in one included, is refused, so repeating a call creates nothing more. Needs the Missing Data feature on for the account. Data points cannot be deleted or switched off with these tools. Nobody is notified and no email is sent. To change a data point afterwards use edit_data_point or set_data_point_defaults.

create_procedure

ChatGPT
Use this when the user asks to set up a new recurring procedure for the team. A procedure (standard operating procedure) is a recurring checklist, daily, weekly or monthly, that team members complete each period. Creates a procedure with a title, recurrence, due_days and steps, and optionally a description, a category and required (true by default). It is assigned to everyone unless assignee_emails names people, and each person named is notified in the app, which cannot be undone. due_days: for daily, the weekdays it is due (1 Monday to 7 Sunday); for weekly, the one weekday it is due; for monthly, the day of the month. Each call creates another procedure. Procedures cannot be switched off or deleted with these tools. To change a procedure use edit_procedure. Procedures are a feature Scanio turns on per account; where it is off, every call says so and does nothing.

create_product_group

ChatGPT
Use this when the user asks to create a product group, for example to group a product line. Creates the group with its name and, optionally, a description, a color and up to 50 products to put in it, which must be tracked by the account. A name that matches an existing group's, in any case, is refused, so repeating a call creates nothing more. If Scanio refuses the products after the group is made, the group stays and the answer names the add_products_to_group call that adds them. Groups cannot be deleted with these tools. Nobody is notified. To change a group use update_product_group.

create_product_merge

ChatGPT
Use this when the user asks to treat two or more listings as one product, for example an old listing and the one that replaced it. A product merge joins an old listing and its replacement, for example a single pack and its case pack, so Scanio reads them as one product: dollar figures add up across members, unit counts stay per member. Merges 2 to 50 ASINs, with primary_asin (one of them) as the merged product's identity, an optional label and an optional pack_label for each member. An ASIN already in a merge cannot join another, so repeating a call is refused. Members the account does not track are merged as they are; with track_missing_products they are also added as products, whose product pages Scanio then checks every day. No one is notified. Merges cannot be undone with these tools. To accept a merge Scanio suggested use confirm_product_merge_suggestion; to change a merge use edit_product_merge.

create_tag

ChatGPT
Use this when the user asks to create a new tag. Creates the tag with its name and, optionally, a color (grey by default), recorded in the tag history under the connected user and marked as made through this connector. A name that matches an existing tag's, in any case, is refused, so repeating a call creates nothing more. Tags cannot be deleted with these tools. Nobody is notified. To put the tag on products use add_tags_to_products or apply_tag_to_group; to rename or recolor a tag use update_tag.

create_task

ChatGPT
Use this when the user asks to create one task, for example a to-do for a teammate about a product or a purchase order. Creates the task in Scanio as the connected user and returns it with its task number and link. Use list_task_categories for category and list_assignees for assignee_email; every ASIN must be a product the account tracks. Give due_date as a date or ISO 8601 time, not a phrase such as "next Friday". When the assignee is someone else, Scanio notifies them in the app and by email (their notification settings apply), and the email cannot be recalled. Each call creates a new task, so repeating it creates a duplicate. For one task per product across many products use create_tasks_bulk; to add to a task that exists use add_task_comment or update_tasks.

create_tasks_bulk

ChatGPT
Use this when the user asks to create a task for each of several products at once, for example a task to update the images of each of ten products. Creates up to 25 tasks as the connected user, one per product. Every item is checked before anything is written: an untracked ASIN, an unknown category or assignee, or a due date that is not a date fails the whole call and names each bad item by its position. An item is skipped when an open task (pending or in progress) already exists for the same product and category, and the answer names that task so you can add to it with add_task_comment. Tasks are created one at a time, so if an error stops the call partway, the tasks already created stay. Each assignee other than the connected user is notified in the app for each task and gets one email for the whole call (their notification settings apply); the email cannot be recalled. For a single task, or one task about several products, use create_task.

create_tasks_from_listing_changes

ChatGPT
Use this when the user wants someone to follow up on detected listing changes, for example a task for each price drop. Creates one task per change, up to 50, each named as list_listing_changes shows it: asin, change_type and detected_on (the first ten characters of detected_at). Each task gets Scanio's title and priority for that kind of change, is created by the connected user and is assigned to no one; a change that already has a task does not get a second, and the answer gives that task's link. If any named change cannot be found, nothing is changed. No one is notified. If Scanio refuses one partway, the call stops: results lists the changes already handled, which must not be sent again, failed the change refused and why, and not_attempted the rest. For a task worded by the user use create_task; to dismiss changes use dismiss_listing_changes.

create_workflow_template

ChatGPT
Use this when the user asks to save a reusable list of workflow steps. A task workflow is an ordered list of steps on a task, often requests to a supplier, each confirmed when done; a workflow template is a saved list of steps a workflow can start from. Creates a template with a name, steps (in order, each a label and optionally email_template, the name of the email template the step starts with; it must match an email template's name exactly, or the step starts with none), and optionally a description; apply_workflow_template starts a task's workflow from it. Template names are unique in an account, so repeating a call is refused and changes nothing. Templates cannot be switched off with these tools. Nobody is notified. To change a template use edit_workflow_template; to copy one use clone_workflow_template. Workflows are a feature Scanio turns on per account; where they are off, every call says so and does nothing.

dismiss_listing_changes

ChatGPT
Use this when the user has reviewed some detected listing changes and wants them cleared from the Change Inbox. Dismisses up to 50 changes, each named as list_listing_changes shows it: asin, change_type and detected_on (the first ten characters of detected_at). A dismissed change cannot be brought back into the inbox, and a change already dismissed is reported, not dismissed twice. If any named change cannot be found, nothing is changed. No one is notified. If Scanio refuses one partway, the call stops: results lists the changes already handled, which must not be sent again, failed the change refused and why, and not_attempted the rest. To dismiss every change of one type use dismiss_listing_changes_by_type; to file tasks for changes use create_tasks_from_listing_changes.

dismiss_listing_changes_by_type

ChatGPT
Use this when the user asks to clear every detected change of one type from the Change Inbox, for example all ranking changes. Dismisses every undismissed change of that change_type, for every product, up to 1,000 per call; remaining says how many are left, so call again while remaining is above 0. A dismissed change cannot be brought back into the inbox, and changes detected since the user last looked are dismissed too, so a repeat can dismiss more. No one is notified. To dismiss particular changes use dismiss_listing_changes.

dismiss_missing_data

ChatGPT
Use this when the user says a piece of missing data is not needed for a product, for example a data point that does not apply to it. Dismisses each cell: it leaves the open list but is kept, and restore_dismissed_missing_data brings it back; a cell already dismissed is reported unchanged. Takes up to 50 cells, each a product (ASIN, or SKU when it has no ASIN) and a data point, each once; every cell must already be tracked (start_tracking_missing_data adds one), and the Missing Data feature must be on for the account. Every cell is checked before anything changes, and a refusal names each bad cell. Nobody is notified and no email is sent. The change is copied to the account's linked Google Sheet, as it is when made in Scanio. If Scanio refuses a change partway, the call stops and the answer lists what changed (updated), what failed and what was not tried. Repeating a call changes nothing more.

dismiss_notifications

ChatGPT
Use this when the user asks to clear notifications away. Dismisses (archives) each named notification, so it leaves the notification bell; restore_notifications brings it back. Takes up to 50 notifications, by the ref list_notifications gives each; only the connected user's own. A notification already in the state asked for is reported, not changed again, and a ref that is not one of the 500 most recent notifications refuses the whole call. If Scanio refuses one partway, the call stops: results lists the notifications already changed, which must not be sent again, failed the one refused and why, and not_attempted the rest. No one is notified.

dismiss_product_merge_suggestions

ChatGPT
Use this when the user turns down merges Scanio suggested. Dismisses up to 50 pending suggestions, each named by from_asin and to_asin (list_product_merges with suggestions "pending" shows them). Scanio never suggests a dismissed pair again, and a suggestion already dismissed is reported, not dismissed twice. A pair already confirmed as a merge, or that is not a suggestion, refuses the whole call. No one is notified. If Scanio refuses a dismissal partway, the call stops: results lists the suggestions already dismissed, which must not be sent again, failed the pair refused and why, and not_attempted the rest. To accept a suggestion use confirm_product_merge_suggestion.

edit_analytics_view

ChatGPT
Use this when the user asks to rename one of their saved Analytics views or change its settings. Changes the connected user's view named by view (an exact match first; a name two views match only in another case is refused): new_name, settings, or both. Only the settings given change; a new_name another view already has is refused. The old view is not kept to undo from. No one is notified. Views cannot be deleted with these tools. To save a new view use save_analytics_view.

edit_bundle

ChatGPT
Use this when the user asks to change a bundle: its bundle listing, its label or the products in it. Changes the bundle named by its bundle_asin, or by its label when it has none (list_bundles shows both); give at least one of bundle_asin, label and component_asins, which replaces the whole component list. A label that matches more than one bundle is refused. The old bundle is not kept to undo from. A product that is part of a product merge (list_product_merges) cannot be in a bundle. ASINs the account does not track are linked as they are; with track_missing_products they are also added as products, whose product pages Scanio then checks every day like the others. No one is notified. Bundles cannot be deleted with these tools. To create a bundle use create_bundle.

edit_contact

ChatGPT
Use this when the user wants to change a contact's details, for example a new email address or phone number. Changes only the fields given, on the contact named by its name or email; an empty string clears a field. An email address another contact already has is refused. An edit already made sends nothing, so repeating a call changes nothing more. Needs the Contacts feature on for the account. Nobody is notified and no email is sent. To add a contact use create_contact; to stop using one use archive_contact.

edit_custom_column

ChatGPT
Use this when the user asks to rename a custom product column or change its data type. Changes the column named by its name or key (list_custom_columns): new_name, data_type, or both. The column keeps its key, so every product keeps its value; the old name and type are not kept to undo from. No one is notified. Columns cannot be deleted with these tools. To add columns use create_custom_columns; to change their order use reorder_custom_columns.

edit_data_point

ChatGPT
Use this when the user wants to rename a data point, change its description or kind, or change whether new products track it. Changes a data point the account created, named by its current name; built-in data points such as MSRP cannot be edited (set_data_point_defaults can still set their default owner and supplier). Give at least one change; a value already as asked is not sent, so repeating a call changes nothing more. Needs the Missing Data feature on for the account. Data points cannot be deleted or switched off with these tools. Nobody is notified and no email is sent. To make a new data point use create_data_point.

edit_procedure

ChatGPT
Use this when the user asks to change a procedure: its title, description, category, whether it is required, its schedule, its steps or who it is assigned to. Changes the procedure named by procedure (its current title, which must match exactly one active procedure); give at least one change. New steps replace the checklist, keeping the progress of any step whose label is unchanged; changing assignees notifies no one. due_days: for daily, the weekdays it is due (1 Monday to 7 Sunday); for weekly, the one weekday it is due; for monthly, the day of the month. Procedures cannot be switched off or deleted with these tools. To create a procedure use create_procedure. Procedures are a feature Scanio turns on per account; where it is off, every call says so and does nothing.

edit_product_merge

ChatGPT
Use this when the user asks to change a product merge: its name, its primary product, its members or their pack labels. Changes the merge named by any ASIN in it (list_product_merges shows them); give at least one change. Only the fields given change; a merge keeps at least 2 members, and an ASIN already in another merge cannot be added. The old merge is not kept to undo from. It never starts tracking new products. No one is notified. Merges cannot be undone with these tools. To merge listings that are not merged yet use create_product_merge.

edit_workflow_step

ChatGPT
Use this when the user asks to change a step of a task's workflow: its label, who is responsible for it or its email template. Changes the step named by its number on the task named by its task number (step numbers are the ones get_task's workflow_steps and Scanio's Workflow tab show); give at least one change. A step has one responsible party, so naming a contact clears the team member and the reverse, and contact_email and user_email are not both given. To add a step use add_workflow_step; to mark one done use confirm_workflow_step. Done as the connected user and recorded in the task's history as done through this connector; nobody is notified in the app. This tool never sends a step's request email (send_workflow_step_email does).

edit_workflow_template

ChatGPT
Use this when the user asks to change one of the account's own workflow templates: its name, description or steps. Changes the template named by template; give at least one of name, description and steps (in order, each a label and optionally email_template, the name of the email template the step starts with; it must match an email template's name exactly, or the step starts with none). New steps replace the list, and a step whose label is unchanged keeps its email_template unless the call sets one. Only workflows started later use the change; tasks already using the template keep their steps. Scanio's built-in templates cannot be edited: copy one with clone_workflow_template, then edit the copy. Templates cannot be switched off with these tools. Nobody is notified. Workflows are a feature Scanio turns on per account; where they are off, every call says so and does nothing.

end_missing_data_snooze

ChatGPT
Use this when the user wants snoozed missing data back on the open list before its snooze ends. Each cell must be snoozed; it goes back to open. Takes up to 50 cells, each a product (ASIN, or SKU when it has no ASIN) and a data point, each once; every cell must already be tracked (start_tracking_missing_data adds one), and the Missing Data feature must be on for the account. Every cell is checked before anything changes, and a refusal names each bad cell. Nobody is notified and no email is sent. The change is copied to the account's linked Google Sheet, as it is when made in Scanio. If Scanio refuses a change partway, the call stops and the answer lists what changed (updated), what failed and what was not tried. To snooze a cell use snooze_missing_data. Repeating a call changes nothing more.

fill_missing_data

ChatGPT
Use this when the user gives the value of a piece of missing product information, for example "the frying pan's MSRP is 44.99". Sets the value on each cell, credited to the connected user; it replaces any value the cell had, which stays in the cell's history, and a cell that already has that value is reported unchanged. Takes up to 50 cells, each a product (ASIN, or SKU when it has no ASIN) and a data point, each once; every cell must already be tracked (start_tracking_missing_data adds one), and the Missing Data feature must be on for the account. Every cell is checked before anything changes, and a refusal names each bad cell. Nobody is notified and no email is sent. The change is copied to the account's linked Google Sheet, as it is when made in Scanio, and the new value to the account's own source sheet when the account has chosen that. If Scanio refuses a change partway, the call stops and the answer lists what changed (updated), what failed and what was not tried. To accept a value a supplier proposed use confirm_proposed_missing_data; to remove a value use clear_missing_data_value. Repeating a call changes nothing more.

find_tasks

ChatGPT
Use this when the user asks about their team's tasks, for example which tasks are overdue, what is assigned to them, or the tasks about a product or a purchase order. Returns tasks with task_number, title, description, status, priority, category, asin, po_number, assignee, creator, due_date, created_at and url (the task in Scanio). A task's status is pending (not started yet), in_progress, completed or cancelled; the status filter also takes open, meaning pending or in progress. With overdue true it returns the open tasks whose due date has passed, most overdue first; otherwise the newest tasks first. Returns 25 tasks by default and at most 200, only tasks the user can see in Scanio. For one task's comments, emails and workflow steps use get_task.

get_ads_by_product

ChatGPT
Use this when the user asks how the ads for particular products performed, for example which advertised products have the highest spend or the lowest return. Returns the account's Amazon Ads results per advertised product (ASIN) from start_date to end_date (at most 731 days), with the product's name, how many campaigns advertise it and in which ad types. Each figure set has impressions, clicks, spend, orders, units, sales (ad sales), orders_promoted, units_promoted and sales_promoted (the advertised product itself), and ctr, cpc, acos (spend / sales), roas (sales / spend) and conversion_rate (orders / clicks), computed over the whole period; a figure is null when Amazon reported none. Money is in currency; rates are fractions (0.25 is 25%). Orders and sales are what Amazon attributes to an ad, within 14 days of an ad click for a vendor (Sponsored Brands and Sponsored Display also count views), counted on the day of that click or view; the last 60 days can still change as Amazon finalizes them, and note says how fresh the figures are. Rows come limit at a time from offset, with total. For results per campaign use list_ad_campaigns.

get_ads_performance

ChatGPT
Use this when the user asks how their Amazon ads performed overall over a period, for example spend, sales and return on ad spend last month. Returns the account's Amazon Ads results (Sponsored Products, Brands and Display) from start_date to end_date, at most 731 days: totals, the same per ad type, and a series by day, week (Monday start) or month. Each figure set has impressions, clicks, spend, orders, units, sales (ad sales), orders_promoted, units_promoted and sales_promoted (the advertised product itself), and ctr, cpc, acos (spend / sales), roas (sales / spend) and conversion_rate (orders / clicks), computed over the whole period; a figure is null when Amazon reported none. Money is in currency; rates are fractions (0.25 is 25%). Orders and sales are what Amazon attributes to an ad, within 14 days of an ad click for a vendor (Sponsored Brands and Sponsored Display also count views), counted on the day of that click or view; the last 60 days can still change as Amazon finalizes them, and note says how fresh the figures are. For results per campaign use list_ad_campaigns; per advertised product use get_ads_by_product.

get_customer_search_terms

ChatGPT
Use this when the user asks which search terms lead shoppers to their products, or how their products rank for a search term. Returns one week of Amazon's search terms report (the latest synced week unless week_start is given): each search term where one of the account's products was among the three most-clicked results, with the term's search frequency rank, its department, and its three most-clicked products (other brands' products included), each with ASIN, name, click-share rank, click share, conversion share and isOwn (true for the account's own product). An empty result means the week has not been synced, or none of the account's products reached the top three for any term that week.

get_enhanced_product_content

ChatGPT
Use this when the user asks about a product's A+ Content, the section of images and text a brand adds to its Amazon product page, for example whether a listing has it or what it says. Returns every A+ Content document linked to the ASIN, approved ones first, each with its name, its status (drafts and rejected documents are included and labeled) and its modules, each with type, headlines, body text and image alt text. Image files are not returned. The content is as of Scanio's last daily sync; an empty list means no document is linked to the ASIN or none has been synced yet. For the bullet points and attributes use get_product.

get_items_bought_together

ChatGPT
Use this when the user asks which items shoppers buy together with their products, for example for bundle or cross-selling ideas. Returns rows from Amazon's weekly market basket report (Sunday-to-Saturday weeks) for the account's products: rank (1 is bought together most often; up to 3 per product per week), purchasedWithAsin (any product, other brands' included), isOwn (true when that item is one of the account's products), combinationPct (from 0 to 1, the share of the product's multi-item orders that also held that item) and asinOrders (the product's own orders that week, or null), which shows how many orders a share is based on. With asin: that product's recent weeks, newest first. Without asin: one week across every product, the pairs found in the most orders first; 25 rows by default and at most 200, with total and hasMore. An empty result means the report has not been synced for that product or week, or it had no multi-item orders.

get_missing_item

ChatGPT
Use this when the user asks about one piece of missing data in detail, especially its emails, for example what a supplier replied about a product's images. Takes a product and a data point and returns the cell's state as list_missing_items gives it; its email conversation (requests, follow-ups and replies, oldest first and numbered, each with direction, from, to, subject, text up to 4,000 characters with body_cut, time and file names; the 30 most recent, with messages_total); who a follow-up would go to now and with what subject (follow_up_to and follow_up_subject), or why one would be refused (follow_up_refused_because); and the files an email can attach (files, with from_conversation for a file that came with a reply). send_missing_data_follow_up and reply_to_missing_data_email take these values.

get_price_and_availability_history

ChatGPT
Use this when the user asks how one product's price, availability, seller or sales rank changed over time, for example when it went out of stock. Returns the daily checks of its Amazon product page, newest first, one row a day: checked_at, title (the page title that day), availability, price, seller (shown as "Sold by"), ranking (the sales rank), back_ordered, carried_forward and reading_note. availability is "In Stock", "Back Order", "Unavailable", "Redirected" (the page now leads to another product or page) or "Doggy" (Scanio's name for Amazon's page-not-found page, shown when the listing no longer exists). carried_forward is true when the page could not be read reliably that day, so the reading repeats the last good one and does not show that the listing was unchanged; reading_note explains an unusual reading in plain words and is null otherwise. Returns 25 rows by default and at most 200, with has_more; narrow it with start_date and end_date. For the changes Scanio flagged across products, such as a price drop or a lost buy box, use list_listing_changes.

get_product

ChatGPT
Use this when the user asks about one product in detail: its listing content, images, attributes, costs or latest purchase order. Returns asin, sku, status, title, brand and product_type; listing (the product page's bullet points for this account's marketplace, in English when available, category, subcategory, list_price, package dimensions, images with their count, largest size and the main image's URL, and attributes such as size, color, flavor and unit_count); costs, with default (the product's default cost), by_vendor (the cost recorded for each vendor code), latest_po (the product's most recent purchase order line: po_number, po_date, vendor_code, net cost and ordered_quantity, or null) and effective (the cost recorded for latest_po's vendor, else the default cost; null when there is no purchase order); and availability, the latest daily check of the product page with the fields list_products describes. No long product description is returned, because none is stored. Returns null for an ASIN this account does not track. To find an ASIN use list_products; for the day-by-day history use get_price_and_availability_history.

get_purchase_order

ChatGPT
Use this when the user asks about one purchase order by its number, for example what it contains or how much of it was accepted or received. Returns the order with po_number, po_date, po_status, vendor_code, ship_to, ship window, delivery window, line_count, totals (ordered_quantity, acknowledged_quantity, the quantity accepted, and received_quantity, over every line) and its lines, sorted by ASIN, each with asin, product_title, vendor_sku, ordered_quantity, acknowledged_quantity, received_quantity, receiving_status, last_receiving_date and unit cost (net_cost_amount in net_cost_currency). Lists at most 200 lines; for a bigger order page through list_purchase_order_lines with po_number. An order the account does not have is answered as not found. To search orders by product or date use list_purchase_order_lines.

get_repeat_purchase_rates

ChatGPT
Use this when the user asks how often customers buy a product again, or how much revenue comes from repeat customers. Returns rows from Amazon's weekly repeat purchase report (Sunday-to-Saturday weeks) for the account's products: orders, uniqueCustomers, repeatCustomersPctTotal (from 0 to 1, the share of those customers who bought again), repeatPurchaseRevenue (amount and currencyCode, revenue from repeat customers before returns) and repeatPurchaseRevenuePctTotal (from 0 to 1, the share of the product's revenue from repeat customers). With asin: that product's recent weeks, newest first. Without asin: one week across every product, ranked by sort_by, highest first; 25 rows by default and at most 200, with total and hasMore. A product with few orders can show an extreme percentage, so read the percentages with orders. An empty result means the report has not been synced for that product or week.

get_sales_and_traffic

ChatGPT
Use this when the user asks how their products sold or how much traffic they got over a period, for example revenue or units by product last month. Returns one row per ASIN from the account's weekly vendor sales reports, highest revenue first: ordered_units, ordered_revenue, shipped_units, shipped_revenue, shipped_cogs (cost of the goods shipped) and glance_views (product page views) summed over the range; conversion_rate (ordered units divided by glance views, null without views); and the latest inventory_units, net_pure_product_margin and mean_forecast_units in the range. The range defaults to the last three months and can span at most twelve. Ordered units, ordered revenue and glance views exist only in the manufacturing view (see distributor_view), so they are null for a row whose figures come from the sourcing view; source_view says which view each row used. Returns 25 rows by default and at most 200, with total and has_more; use offset for more. For every weekly metric week by week use get_weekly_retail_metrics; for the products that changed most between two periods use get_top_gaining_and_declining_products.

get_sales_drop_alerts

ChatGPT
Use this when the user asks which products had a big drop in sales recently, for example last week. Returns the products whose sales fell by half or more in the latest weekly sales report compared with the week before, most severe first, each with asin, title, metric (ordered_units, ordered_revenue, shipped_units or shipped_revenue), current, previous and pct_change, with count. Ordered units and revenue are compared where Amazon reported them the week before (a product that left the report counts as falling to nothing), shipped units and revenue otherwise. Empty when fewer than two weeks are synced or nothing fell that far. For the biggest changes in either direction, or over a month or custom dates, use get_top_gaining_and_declining_products.

get_task

ChatGPT
Use this when the user asks about one task in detail: its comments, its emails, its linked products or its workflow steps. Takes a task number (find_tasks lists them) and returns the task's fields (title, description, status, priority, category, ASIN, SKU, purchase order number, due date, assignee, creator, who completed it, and for a product review task the ASIN under review), the products linked to it, its watchers, its 50 most recent comments with the names of their attached files, the 20 most recent emails on it with sender, recipients and text (each up to 4,000 characters; body_cut says when it was cut), and its workflow steps, numbered as Scanio shows them, which is how edit_workflow_step and confirm_workflow_step name a step. comments_total and emails_total give the full counts. To search tasks use find_tasks.

get_top_gaining_and_declining_products

ChatGPT
Use this when the user asks which products grew or declined the most between two periods, for example the biggest gainers and decliners this week or this month. Compares one figure (metric) between the latest synced week and the week before (period week, the default), the latest month and the month before (month), or two custom ranges, from the account's weekly vendor sales reports. Returns gainers and decliners separately, each up to limit, largest change first, or largest impact_pct first with sort_by impact. Each has asin, title, vendor_sku, current, previous, change, pct_change, impact_pct (the change as a share of the account's total for the current period), share_pct and merged (a product merge's label and members, or null). Ordered units, ordered revenue and glance views exist only in the manufacturing view, so with distributor_view sourcing they come back empty with a note. Only settled report periods are compared, never the last 24 hours. For drops of half or more in the latest week use get_sales_drop_alerts; to compare chosen products use compare_products_between_periods.

get_weekly_retail_metrics

ChatGPT
Use this when the user asks for detailed weekly figures beyond sales and traffic, such as returns, lost buy box, net margin, inventory health, sell-through, fill rate or vendor lead time, per product and week. Returns every weekly retail metric Amazon reports to the vendor, per ASIN and week, for the weeks whose Sunday falls between start_date and end_date (13 weeks at most; the dates at most 90 days apart), synced daily and kept two years back. metrics narrows the figures and asins the products. Each row has asin, title, week_start, week_end, source_view, currency_code and one value per metric, null when Amazon reported none. Money is in currency_code; rates are fractions (0.25 is 25%) and vendor_lead_time_days is days; inventory figures are null in weeks older than 8 weeks, and the sourcing view has no orders or traffic. Rows come largest shipped revenue first within each week, limit at a time from offset, with total. totals has a row per week: Amazon's own figures for the whole account in the manufacturing and sourcing views (basis amazon); with all, or when asins is given, the sum of the rows (basis rows) for counts, money and inventory, and null for rates, averages and per-unit figures. coverage gives the first and last week stored per view; when none is stored, note says the figures have not been synced yet. For sales and traffic totals over a longer range use get_sales_and_traffic.

list_ad_campaigns

ChatGPT
Use this when the user asks how their individual ad campaigns performed, for example which campaigns spent the most. Returns the account's Amazon Ads campaigns from start_date to end_date (at most 731 days), one row per campaign with its latest name, ad type, delivery status and budget, and its results over the period. Each figure set has impressions, clicks, spend, orders, units, sales (ad sales), orders_promoted, units_promoted and sales_promoted (the advertised product itself), and ctr, cpc, acos (spend / sales), roas (sales / spend) and conversion_rate (orders / clicks), computed over the whole period; a figure is null when Amazon reported none. Money is in currency; rates are fractions (0.25 is 25%). Orders and sales are what Amazon attributes to an ad, within 14 days of an ad click for a vendor (Sponsored Brands and Sponsored Display also count views), counted on the day of that click or view; the last 60 days can still change as Amazon finalizes them, and note says how fresh the figures are. Rows come limit at a time from offset, with total. For the account's totals use get_ads_performance.

list_all_procedures

ChatGPT
Use this when the user asks which procedures the account has, not only their own. A procedure (standard operating procedure) is a recurring checklist, daily, weekly or monthly, that team members complete each period. Returns every active procedure, newest first, with title, description, category, recurrence, due_days, required, steps, assigned_to_everyone, assignee_count, creator and created_at, a page at a time (page, limit, total, has_more). Needs permission to create, manage or approve procedures. For the connected user's own procedures and their progress use list_my_procedures. Procedures are a feature Scanio turns on per account; where it is off, every call says so and does nothing.

list_analytics_views

ChatGPT
Use this when the user asks about their saved views of Scanio's Analytics page, or wants a link that opens one. Returns the connected user's own saved views (a saved view belongs to one person), most recently changed first: name, settings (start_date, end_date, asin, granularity, metrics, tab, and for the trends tab compare_asins, comparison_mode, compare_metrics and hide_sparse; a setting the view does not set is left out), url (the Analytics page opened with those settings) and updated_at, with total.

list_assignees

ChatGPT
Use this when you need the team members a task can be assigned to, for example to turn a name the user mentions into the email address the task tools take. Returns each member's name and email, the same people the Tasks page offers as assignees. Only these emails are accepted as create_task's assignee_email and as update_tasks' assignee or watchers.

list_bundles

ChatGPT
Use this when the user asks about their bundles: products sold as a bundle listing (for example a variety pack) linked to the component products they contain, so Scanio can show them as one row. Returns the account's bundles, newest first, each with bundle_asin (the bundle listing, or null for a bundle with only a label), label, created_from (manual or suggestion), components (the component ASINs) and created_at, with total and has_more. With include_suggestions it also returns Scanio's current bundle suggestions: listings whose title reads like a bundle and that have no sales or purchase orders of their own, each with bundle_asin, title, sku, confidence (high when the listing has traffic, else medium), has_traffic and suggested_components (most similar first). Returns 50 bundles by default and at most 200; use offset for more.

list_contacts

ChatGPT
Use this when you need the outside people the account works with, usually suppliers, for example to find a supplier's email address before emailing them or making them responsible for missing data. Returns each contact's name, email (one address, or several separated by commas for a shared inbox), organization, role, phone, notes and archived (an archived contact cannot be emailed). Archived contacts are left out unless include_archived is true. Returns 100 contacts by default and at most 200, with has_more. For the account's own team members use list_assignees.

list_custom_columns

ChatGPT
Use this when you need the extra product columns the account added in Scanio, for example before setting a product's value in one. Returns each custom column in the order the Products page shows them: name, key (its stable identifier, which stays the same when the column is renamed), data_type (text, number or date) and position (1 is first), with total. To set a product's value use update_products with custom_fields.

list_data_points

ChatGPT
Use this when you need the pieces of product information the account collects, its data points (the columns of the Missing Data grid, such as MSRP or Images), for example to find a data point's exact name or who is responsible for it by default. Returns each data point's name, description, kind (column: a cell for every product; per_product: tracked only for some products), added_to_new_products, active, built_in (built-in data points cannot be renamed), default owner (a teammate) and default supplier (a contact). Inactive data points are left out unless include_inactive is true. For the missing values themselves use list_missing_items.

list_listing_changes

ChatGPT
Use this when the user asks what changed on their product listings, for example price or availability changes, a lost buy box or a new title. Returns the changes Scanio detected (the account's Change Inbox), newest first, each with asin, product_title, product_sku, change_type, old_value, new_value, detected_at and dismissed. change_type is price, availability, buy_box (who holds the buy box), ranking (sales rank), title or bullets (the bullet points). Dismissed changes are left out unless include_dismissed is true. Returns 25 changes by default and at most 200; while has_more is true, pass next_cursor as cursor for the next page. For one product's day-by-day readings use get_price_and_availability_history.

list_missing_items

ChatGPT
Use this when the user asks what product information is still missing or what a supplier still owes, for example which products have no MSRP or what is waiting on a supplier. Returns Missing Data cells, one per product and data point: asin (or sku for a product with no ASIN), product_title, data_point, status (open, filled, snoozed, dismissed, or awaiting_confirmation when a supplier's email reply or the linked Google Sheet proposed a value, given in proposed_value with proposed_by), the filled value, snoozed_until, notes, the owner (a teammate) and supplier (a contact) with their email addresses (the cell's own, else the data point's default), in_progress, the task_number it came from and waiting_since. Lists open cells unless status says otherwise (a snooze that has ended counts as open). Returns 50 cells by default and at most 200, with has_more. For one cell's email conversation use get_missing_item.

list_my_procedures

ChatGPT
Use this when the user asks which procedures they have to do, or how far along their checklists are. A procedure (standard operating procedure) is a recurring checklist, daily, weekly or monthly, that team members complete each period. Returns the procedures assigned to the connected user, each with title, category, recurrence, due_days, required, steps (the checklist, in order), period (the current period's first day), due_on (the day it is due; both null for a daily procedure on a day it is not due) and completion for this period (null before it is started; else status (in_progress, pending_approval, completed, approved or rejected), done_steps, open_steps, notes, late, completed_at and rejection_note). For every procedure in the account use list_all_procedures. Procedures are a feature Scanio turns on per account; where it is off, every call says so and does nothing.

list_notifications

ChatGPT
Use this when the user asks about their Scanio notifications, for example what is new or what they have not read. Returns the connected user's own in-app notifications about this account (never a teammate's), newest first: ref (the handle the other notification tools take), type, title, message, read, from (who caused it), link (where it leads in Scanio), task_url (the task it is about, or null) and created_at, with total, page, has_more and unread (how many are unread and not dismissed). With archived it lists the dismissed ones instead. Returns 20 by default and at most 50; use page for older ones.

list_procedures_awaiting_approval

ChatGPT
Use this when a manager asks which completed procedure checklists are waiting for their approval. Returns the checklists submitted before their due day and waiting for a manager, each with procedure (its title), person, person_email, period, submitted_at and notes. Needs permission to approve procedures. To decide on them use approve_procedure_checklists or reject_procedure_checklists. Procedures are a feature Scanio turns on per account; where it is off, every call says so and does nothing.

list_product_groups

ChatGPT
Use this when the user asks which product groups the account has or which products are in a group. Returns each group with its name, description, color, member_count and asins (its products, sorted, at most 200; for a bigger group page through list_products with group), with total, the number of groups listed. group returns one group by name. The group tools take these names.

list_product_merges

ChatGPT
Use this when the user asks which products are merged, or which merges Scanio suggests. A product merge joins an old listing and its replacement, for example a single pack and its case pack, so Scanio reads them as one product: dollar figures add up across members, unit counts stay per member. Returns the account's merges, newest first, each with primary_asin (the merged product's identity), label, created_from (manual or suggestion), members (asin and pack_label) and created_at, with total and has_more. With suggestions it also returns Scanio's merge suggestions in that state (a listing that started redirecting to another): from_asin, from_title, to_asin, to_title, to_is_tracked, status and created_at. Returns 50 merges by default and at most 200; use offset for more.

list_products

ChatGPT
Use this when the user wants to find or browse the products their Scanio account tracks, for example by name, SKU, brand, tag, product group or current availability. Returns products sorted by title, each with asin, sku, title, brand, status, tags, group (the first alphabetically when a product is in several) and the latest daily check of its Amazon product page: availability, price, seller, ranking, back_ordered, checked_at, carried_forward and reading_note. availability is "In Stock", "Back Order", "Unavailable", "Redirected" (the page now leads to another product or page) or "Doggy" (Scanio's name for Amazon's page-not-found page, shown when the listing no longer exists). carried_forward is true when the page could not be read reliably that day, so the reading repeats the last good one and does not show that the listing was unchanged; reading_note explains an unusual reading in plain words and is null otherwise. Lists active products unless status says otherwise. Returns 25 products by default and at most 200, with total and has_more; use offset for the next page. For one product's full details, costs and listing content use get_product.

list_purchase_order_lines

ChatGPT
Use this when the user asks about purchase orders across products or dates, for example the open orders for an ASIN, the orders placed last month, or how much of an order was accepted or received. Returns purchase order lines, newest order first, each with the order's po_number, po_date, po_status, vendor_code, ship_to, ship window and delivery window, and the line's asin, product_title, vendor_sku (the account's SKU when the product is tracked, otherwise the SKU on the order), ordered_quantity, acknowledged_quantity (the quantity accepted), received_quantity, receiving_status, last_receiving_date and unit cost (net_cost_amount in net_cost_currency). Orders created more than about 180 days before the account was connected appear only if they were imported from a file. Returns 25 lines by default and at most 200, with total and has_more; use offset for more. For one whole order with its totals use get_purchase_order.

list_tags

ChatGPT
Use this when the user asks which tags the account uses, how many products carry a tag, or who tagged or untagged a product and when. Returns every tag with its name, color and product_count, with total_tags, and the newest tag history, newest first: each entry has tag, asin (for a tag put on or taken off a product), action (tag_applied, tag_removed, tag_created, tag_renamed, tag_color_changed or tag_deleted), old_value, new_value, user (who made the change), via_connector (true when it was made through this connector) and changed_at. tag or asin narrows the history to one tag or one product. While history_has_more is true, pass history_next_cursor as history_cursor for older entries. To find the products that carry a tag use list_products with tag.

list_task_categories

ChatGPT
Use this when you need the task categories the account uses, for example before creating a task or changing its category. Returns each category's name and whether it is built in. Use these names as the category in create_task, create_tasks_bulk and update_tasks.

list_task_workflows

ChatGPT
Use this when the user asks how their task workflows are going, for example which ones are stuck and on which step. A task workflow is an ordered list of steps on a task, often requests to a supplier, each confirmed when done; a workflow template is a saved list of steps a workflow can start from. Returns every task with a workflow that the user can see in Scanio's Tasks list, longest waiting first, each with task_number, title, task_url, task_status, template (the template it started from), steps_total, steps_confirmed, progress_pct, bucket (how long the current step has waited: on_track up to 3 days, attention 4 to 7, stalled 8 to 14, critical 15 or more) and current_step (null when every step is confirmed or skipped; else label, status (pending, requested or received), responsible and responsible_kind (user or contact), stuck_since and stuck_days), a page at a time (page, limit, has_more). summary counts every workflow the user can see, whatever the filters: on_track, attention, stalled, critical, completed, total and completed_this_week. With include_templates it also returns the account's workflow templates (name, description, built_in, and steps with label and email_template). For one task's steps in detail use get_task. Workflows are a feature Scanio turns on per account; where they are off, every call says so and does nothing.

mark_all_notifications_read

ChatGPT
Use this when the user asks to mark all their notifications as read. Marks every unread notification the connected user has about this account as read and says how many. The earlier read states are not kept, so they cannot be put back as they were; mark_notifications_unread can mark named ones unread again. No one is notified. To mark only some read use mark_notifications_read.

mark_missing_data_in_progress

ChatGPT
Use this when the user says the team has started gathering the missing data for some products. Flags each product's outstanding cells as in progress, gives cells with no owner the data point's default owner, and starts tracking every active data point the product does not track yet. Takes products only (ASIN, or SKU when it has no ASIN), up to 50. The change is copied to the account's linked Google Sheet, as it is when made in Scanio. Needs the Missing Data feature on for the account. Nobody is notified and no email is sent. Repeating a call changes nothing more. To remove the flag use clear_missing_data_in_progress.

mark_notifications_read

ChatGPT
Use this when the user asks to mark particular notifications as read. Marks each named notification read; marking a task's notification read also marks that task as seen. Takes up to 50 notifications, by the ref list_notifications gives each; only the connected user's own. A notification already in the state asked for is reported, not changed again, and a ref that is not one of the 500 most recent notifications refuses the whole call. If Scanio refuses one partway, the call stops: results lists the notifications already changed, which must not be sent again, failed the one refused and why, and not_attempted the rest. No one is notified. To mark every unread notification read use mark_all_notifications_read; to mark some unread use mark_notifications_unread.

mark_notifications_unread

ChatGPT
Use this when the user asks to mark notifications as unread, for example to come back to them later. Marks each named notification unread. Takes up to 50 notifications, by the ref list_notifications gives each; only the connected user's own. A notification already in the state asked for is reported, not changed again, and a ref that is not one of the 500 most recent notifications refuses the whole call. If Scanio refuses one partway, the call stops: results lists the notifications already changed, which must not be sent again, failed the one refused and why, and not_attempted the rest. No one is notified. To mark them read use mark_notifications_read.

preview_all_missing_data_requests

ChatGPT
Use this when the user wants to email everyone who still owes missing product data, before anything is sent: it shows exactly what send_all_missing_data_requests would send right now and sends nothing. Returns one summary email per person responsible for open Missing Data cells (each cell's owner or supplier, a data point's default included), each with the recipient's address and name, how many items it lists, its subject, its text (up to 4,000 characters; body_cut says when it was cut) and its digest (a code that identifies exactly that email, which send_all_missing_data_requests takes back); the open items nobody can be emailed about, and why; and daily_emails_left, how many more emails this connection may send in the next 24 hours. Show the user every email before any is sent.

reject_procedure_checklists

ChatGPT
Use this when a manager turns down procedure checklists that were handed in early and are waiting for approval (list_procedures_awaiting_approval lists them), for example because a step was not really done. Rejects each one with a note saying why, and each submitter is notified in the app with the note, which cannot be undone. Takes up to 50 checklists, each named by procedure, person (the submitter's email) and period. Nobody may decide on their own checklist. If any named checklist is not waiting for approval, nothing is changed, so repeating a call changes nothing. If Scanio refuses one partway, the call stops: results lists the decisions made, which must not be sent again, failed the one refused and why, and not_attempted the rest, each named by procedure, person and period. Procedures are a feature Scanio turns on per account; where it is off, every call says so and does nothing. To accept checklists use approve_procedure_checklists.

reject_proposed_missing_data

ChatGPT
Use this when the user turns down a value a supplier proposed for cells waiting for confirmation (status awaiting_confirmation in list_missing_items). Each cell goes back to open; the rejected value, and the reason when given, stay in its history. Takes up to 50 cells, each a product (ASIN, or SKU when it has no ASIN) and a data point, each once; every cell must already be tracked (start_tracking_missing_data adds one), and the Missing Data feature must be on for the account. Every cell is checked before anything changes, and a refusal names each bad cell. Nobody is notified and no email is sent. The change is copied to the account's linked Google Sheet, as it is when made in Scanio. If Scanio refuses a change partway, the call stops and the answer lists what changed (updated), what failed and what was not tried. To accept a proposal use confirm_proposed_missing_data. Repeating a call changes nothing more.

remove_products_from_group

ChatGPT
Use this when the user asks to take products out of a product group. Removes up to 50 products from the group named by group; they stay in Scanio and keep their tags. The answer lists the products removed and those that were not in the group, so repeating a call changes nothing more. Nobody is notified. To put products in use add_products_to_group.

remove_tags_from_products

ChatGPT
Use this when the user asks to take tags off products. Removes each named tag from up to 50 of the account's products, the same change as the tag editor in Scanio, recorded in the tag history under the connected user and marked as made through this connector. The tags must exist and every product must be tracked by the account, or nothing is changed. The tags themselves are kept. The answer lists, for each tag, the products untagged and those that did not have it, so repeating a call changes nothing more. Nobody is notified. To put tags on use add_tags_to_products.

reorder_custom_columns

ChatGPT
Use this when the user asks to change the order of the custom product columns. The columns named move to the front in the order given, and the others keep their order after them; the earlier order is not kept to undo from. No one is notified. To add columns use create_custom_columns; to rename one use edit_custom_column.

reply_to_missing_data_email

ChatGPT
Use this when the user wants to answer an email received about a piece of missing data, for example a supplier's question about a request. Replies to one received message in the cell's conversation (reply_to_message, its number in get_missing_item; the newest received message when left out), to its sender, with the earlier message quoted below the text; files attaches files the cell already has. The sender must be a team member, a contact, or someone Scanio emailed about the cell. Show the user the whole email first and give recipient_email as the sender's address shown: if the message came from someone else, nothing is sent. The email goes from Scanio in the user's name, to someone outside the account when it is a supplier. A sent email cannot be recalled. If Scanio fails or runs out of time while sending, the email may already have gone: the answer says so and where to check, and it must not be sent again before that. It counts toward the 30 emails this connection may send in 24 hours; over that, nothing is sent and the answer says when more may go. The answer says whether the email was sent; where email sending is switched off for the account, nothing is sent and the answer says so. Repeating the call sends the reply again.

restore_dismissed_missing_data

ChatGPT
Use this when the user wants dismissed missing data back on the open list. Each cell must be dismissed; it goes back to open. Takes up to 50 cells, each a product (ASIN, or SKU when it has no ASIN) and a data point, each once; every cell must already be tracked (start_tracking_missing_data adds one), and the Missing Data feature must be on for the account. Every cell is checked before anything changes, and a refusal names each bad cell. Nobody is notified and no email is sent. The change is copied to the account's linked Google Sheet, as it is when made in Scanio. If Scanio refuses a change partway, the call stops and the answer lists what changed (updated), what failed and what was not tried. To dismiss a cell use dismiss_missing_data. Repeating a call changes nothing more.

restore_notifications

ChatGPT
Use this when the user asks to bring back notifications they dismissed. Restores each named dismissed notification to the notification bell; list_notifications with archived lists the dismissed ones and their refs. Takes up to 50 notifications, by the ref list_notifications gives each; only the connected user's own. A notification already in the state asked for is reported, not changed again, and a ref that is not one of the 500 most recent notifications refuses the whole call. If Scanio refuses one partway, the call stops: results lists the notifications already changed, which must not be sent again, failed the one refused and why, and not_attempted the rest. No one is notified. To dismiss notifications use dismiss_notifications.

save_analytics_view

ChatGPT
Use this when the user asks to save a view of Scanio's Analytics page, for example last quarter's revenue for one product, to open again later. Saves a new view with a name and its settings for the connected user; it appears in their Analytics page's "Saved views" menu. A view with the same name is refused, so repeating the call saves nothing new. No one is notified. Views cannot be deleted with these tools. To change a saved view use edit_analytics_view.

save_procedure_checklist

ChatGPT
Use this when the user reports progress on one of their procedure checklists, for example steps they finished, without handing it in. On this period's checklist of a procedure assigned to the connected user (only their own), named by its title, ticks the steps in check, unticks those in uncheck and saves notes; give at least one. It starts the checklist first if it is not open. A step cannot be both ticked and unticked, and a checklist already submitted for this period cannot be changed. Nobody is notified. To hand it in use submit_procedure_checklist. Procedures are a feature Scanio turns on per account; where it is off, every call says so and does nothing.

send_all_missing_data_requests

ChatGPT
Use this when the user has seen the emails from preview_all_missing_data_requests and asks to send them. Emails each person responsible for open Missing Data cells one summary of what they still owe, from Scanio in the user's name, mostly to suppliers outside the account. Give expected_recipients and expected_digests exactly as the preview listed them: if the summaries would now go to anyone else or say anything different (an item added or removed since the preview), nothing is sent and the answer says what changed, so preview again. A sent email cannot be recalled. If Scanio fails or runs out of time while sending, the email may already have gone: the answer says so and where to check, and it must not be sent again before that. Each recipient counts toward the 30 emails this connection may send in 24 hours; over that, nothing is sent and the answer says when more may go. The answer says whether the email was sent; where email sending is switched off for the account, nothing is sent and the answer says so. Repeating the call sends every summary again. To email about one product's data use send_missing_data_request.

send_missing_data_follow_up

ChatGPT
Use this when the user wants to remind someone about a missing data request that was sent and not answered. Sends a follow-up in the cell's latest request conversation, to whoever that request went to (follow_up_to in get_missing_item), under the subject Scanio gives it (follow_up_subject in get_missing_item), with the earlier message quoted below the text; files attaches files the cell already has. Show the user the whole email first and give recipient_email and subject exactly as get_missing_item showed them: if either would now be different, nothing is sent. The email goes from Scanio in the user's name, to someone outside the account when it is a supplier. A sent email cannot be recalled. If Scanio fails or runs out of time while sending, the email may already have gone: the answer says so and where to check, and it must not be sent again before that. It counts toward the 30 emails this connection may send in 24 hours; over that, nothing is sent and the answer says when more may go. The answer says whether the email was sent; where email sending is switched off for the account, nothing is sent and the answer says so. Repeating the call sends the email again. To send a first request use send_missing_data_request.

send_missing_data_request

ChatGPT
Use this when the user asks to email one person to request one piece of missing product data, for example to ask a supplier for a product's images. Sends one email about one Missing Data cell (a product and a data point) to the cell's owner (a team member) or its supplier (a contact), as to says, with the subject and text given; files attaches files the cell already has. Show the user the whole email first and give recipient_email exactly as shown: if that person now has another address, nothing is sent. The cell must already be tracked. The email goes from Scanio in the user's name, to someone outside the account when it is a supplier. A sent email cannot be recalled. If Scanio fails or runs out of time while sending, the email may already have gone: the answer says so and where to check, and it must not be sent again before that. It counts toward the 30 emails this connection may send in 24 hours; over that, nothing is sent and the answer says when more may go. The answer says whether the email was sent; where email sending is switched off for the account, nothing is sent and the answer says so. Repeating the call sends the email again. To follow up on a request already sent use send_missing_data_follow_up; to answer a reply use reply_to_missing_data_email; to email everyone who owes data use send_all_missing_data_requests.

send_task_email

ChatGPT
Use this when the user asks to email someone about a task, usually a supplier, or to answer an email the task received. Sends an email from the task, named by its task number, to the addresses in to and cc, with the subject and text given; files attaches files already on the task. Replies come back to the task. To answer an email the task received, give reply_to_latest_from (its sender's address): the newest email from them is answered in the same thread, quoted below the text. Show the user the whole email first; it goes exactly as written ({{placeholders}} are refused). Every recipient must be a team member, a contact, or someone already on the task's emails; add a new supplier with create_contact first. The email goes from Scanio in the user's name, usually to a supplier outside the account. A sent email cannot be recalled. If Scanio fails or runs out of time while sending, the email may already have gone: the answer says so and where to check, and it must not be sent again before that. It counts toward the 30 emails this connection may send in 24 hours; over that, nothing is sent and the answer says when more may go. The answer says whether the email was sent; where email sending is switched off for the account, nothing is sent and the answer says so. Repeating the call sends the email again.

send_workflow_step_email

ChatGPT
Use this when the user asks to send the request email of a step in a task's workflow, for example the step that asks a supplier for a certificate. Sends the email to the step's responsible contact or team member, plus any also_to addresses, then marks the step requested and keeps its Missing Data cell in step. Name the task by its task number and the step by its number as get_task shows it. Show the user the whole email first and give recipient_email as the step's address shown: if the step now goes to someone else, nothing is sent. subject and body go exactly as written (the step's email template is not applied); files are the task's own files, by name. Extra addresses must be team members, contacts or people already on the task's emails. The email goes from Scanio in the user's name, usually to a supplier outside the account. A sent email cannot be recalled. If Scanio fails or runs out of time while sending, the email may already have gone: the answer says so and where to check, and it must not be sent again before that. It counts toward the 30 emails this connection may send in 24 hours; over that, nothing is sent and the answer says when more may go. The answer says whether the email was sent; where email sending is switched off for the account, nothing is sent and the answer says so. Repeating the call sends the request again.

set_data_point_defaults

ChatGPT
Use this when the user wants to set who is responsible by default for a data point: its default owner (a team member) and default supplier (a contact), which every cell that names nobody of its own falls back to. Give at least one of the two; null removes one. Works on any active column, built-in ones included, but not on a per_product data point or one switched off. A value already as asked is not sent, so repeating a call changes nothing more. Needs the Missing Data feature on for the account. Data points cannot be deleted or switched off with these tools. Nobody is notified and no email is sent. To change who is responsible for particular cells use assign_missing_data.

snooze_missing_data

ChatGPT
Use this when the user wants to set missing data aside until a date, for example because the supplier will only have it next month. Snoozes each cell until snooze_until and can save a note; a snoozed cell is not listed as open until then. Takes up to 50 cells, each a product (ASIN, or SKU when it has no ASIN) and a data point, each once; every cell must already be tracked (start_tracking_missing_data adds one), and the Missing Data feature must be on for the account. Every cell is checked before anything changes, and a refusal names each bad cell. Nobody is notified and no email is sent. The change is copied to the account's linked Google Sheet, as it is when made in Scanio. If Scanio refuses a change partway, the call stops and the answer lists what changed (updated), what failed and what was not tried. To end a snooze early use end_missing_data_snooze. Repeating a call changes nothing more.

start_procedure_checklist

ChatGPT
Use this when the user says they are starting this period's checklist of one of their procedures. Opens this period's checklist of a procedure assigned to the connected user (only their own), named by its title; nothing changes when it is open already, and a daily procedure opens only on a day it is due. Nobody is notified. Then save_procedure_checklist ticks steps and submit_procedure_checklist hands it in. Procedures are a feature Scanio turns on per account; where it is off, every call says so and does nothing.

start_tracking_missing_data

ChatGPT
Use this when the user wants Scanio to start collecting a piece of product information for products that do not track it yet, for example to start tracking Images for three new products. Creates an open cell for each product and data point, owned by the data point's default owner and supplier until assign_missing_data changes them. Takes up to 50 products and 20 data points, at most 50 cells in all. A data point that is switched off is refused, and a cell the product already has, in any state, is reported and not created again (restore_dismissed_missing_data brings back a dismissed one). The change is copied to the account's linked Google Sheet, as it is when made in Scanio. Needs the Missing Data feature on for the account. Nobody is notified and no email is sent. Repeating a call changes nothing more. If Scanio refuses a cell partway, the call stops and the answer lists what was tracked, what failed and what was not tried. To flag products as being worked on use mark_missing_data_in_progress.

submit_procedure_checklist

ChatGPT
Use this when the user says they finished one of their procedure checklists and want to hand it in. Hands in this period's checklist of a procedure assigned to the connected user (only their own), named by its title, after ticking or unticking steps (check, uncheck) and saving notes when given; it starts the checklist if it is not open. With every step ticked it is completed, or, before the procedure's due day, held for a manager's approval, and then every admin and manager in the account is notified in the app, which cannot be undone; with steps still open it stays in progress and the answer lists them. A checklist already submitted for this period cannot be changed, so repeating a submit changes nothing. To save progress without handing it in use save_procedure_checklist. Procedures are a feature Scanio turns on per account; where it is off, every call says so and does nothing.

update_product_group

ChatGPT
Use this when the user asks to rename a product group or change its description or color. Changes the group named by group; give at least one of name, description and color. A new name may not match another group's, even in case alone, and a change that changes nothing is not sent, so repeating a call changes nothing more. Groups cannot be deleted with these tools. Nobody is notified. To change which products are in the group use add_products_to_group or remove_products_from_group.

update_products

ChatGPT
Use this when the user asks to change products the account tracks: their details, custom column values, archiving or snoozing. Changes up to 50 products, each with its own changes: sku, title, brand, upc, vendor_code, category, subcategory, comment and notes (null clears one), custom_fields, archived (an archived product is hidden, never deleted) and snoozed (7 days). A product's cost per vendor cannot be changed here. Every product must be tracked and every custom column must exist, or nothing is changed; a few reserved custom column keys cannot be set here. A value already as asked is not sent, so repeating a call changes nothing more. The answer gives, for each product, what changed and whether it is now archived and snoozed. If Scanio stops partway (for example at its limit of 100 changes a minute), stopped says why and not_done lists what was not done. Nobody is notified. To add new products use add_products; for tags and groups use the tag and group tools.

update_tag

ChatGPT
Use this when the user asks to rename a tag or change its color. Changes the tag named by tag; give a new name, a new color, or both. A new name may not match another tag's, even in case alone, and a change that changes nothing is not sent, so repeating a call changes nothing more. The change is recorded in the tag history under the connected user and marked as made through this connector. Tags cannot be deleted with these tools. Nobody is notified. To make a new tag use create_tag.

update_tasks

ChatGPT
Use this when the user asks to change tasks that exist: complete or cancel them, reassign them, change their due date, priority, category, title or description, or add or remove watchers. Changes up to 50 tasks, each named by its task number with its own changes. Setting status completed or cancelled presses Scanio's Complete or Cancel button from any other status; pending or in_progress reopens a completed or cancelled task first. Changes are made as the connected user, with their Scanio permissions, and each task's history shows them as made through this connector. A new assignee is notified, and so are a completed task's assignee (or its creator) and watchers, in the app and by email, one email per person for the whole call (their notification settings apply); an email cannot be recalled. New watchers are told in the app. Every task number and value is checked before anything changes, and each task in the answer lists what changed. If Scanio refuses a change partway, the call stops: the answer lists the tasks changed, the task that failed with what had already changed on it, and the tasks not tried. Values already as asked are left alone and nobody is notified again, so repeating a call changes nothing more. To add a comment use add_task_comment; to link products use link_products_to_task.

add_products

Claude

add_products_to_group

Claude

add_tags_to_products

Claude

add_task_comment

Claude

add_workflow_step

Claude

apply_tag_to_group

Claude

apply_workflow_template

Claude

approve_procedure_checklists

Claude

archive_contact

Claude

assign_missing_data

Claude

attach_file_to_missing_data

Claude

clear_missing_data_in_progress

Claude

clear_missing_data_value

Claude

clone_workflow_template

Claude

compare_products_between_periods

Claude

confirm_bundle_suggestions

Claude

confirm_product_merge_suggestion

Claude

confirm_proposed_missing_data

Claude

confirm_workflow_step

Claude

create_bundle

Claude

create_contact

Claude

create_custom_columns

Claude

create_data_point

Claude

create_procedure

Claude

create_product_group

Claude

create_product_merge

Claude

create_tag

Claude

create_task

Claude

create_tasks_bulk

Claude

create_tasks_from_listing_changes

Claude

create_workflow_template

Claude

dismiss_listing_changes

Claude

dismiss_listing_changes_by_type

Claude

dismiss_missing_data

Claude

dismiss_notifications

Claude

dismiss_product_merge_suggestions

Claude

edit_analytics_view

Claude

edit_bundle

Claude

edit_contact

Claude

edit_custom_column

Claude

edit_data_point

Claude

edit_procedure

Claude

edit_product_merge

Claude

edit_workflow_step

Claude

edit_workflow_template

Claude

end_missing_data_snooze

Claude

fill_missing_data

Claude

find_tasks

Claude

get_customer_search_terms

Claude

get_enhanced_product_content

Claude

get_items_bought_together

Claude

get_missing_item

Claude

get_price_and_availability_history

Claude

get_product

Claude

get_purchase_order

Claude

get_repeat_purchase_rates

Claude

get_sales_and_traffic

Claude

get_sales_drop_alerts

Claude

get_task

Claude

get_top_gaining_and_declining_products

Claude

get_weekly_retail_metrics

Claude

list_all_procedures

Claude

list_analytics_views

Claude

list_assignees

Claude

list_bundles

Claude

list_contacts

Claude

list_custom_columns

Claude

list_data_points

Claude

list_listing_changes

Claude

list_missing_items

Claude

list_my_procedures

Claude

list_notifications

Claude

list_procedures_awaiting_approval

Claude

list_product_groups

Claude

list_product_merges

Claude

list_products

Claude

list_purchase_order_lines

Claude

list_tags

Claude

list_task_categories

Claude

list_task_workflows

Claude

mark_all_notifications_read

Claude

mark_missing_data_in_progress

Claude

mark_notifications_read

Claude

mark_notifications_unread

Claude

preview_all_missing_data_requests

Claude

reject_procedure_checklists

Claude

reject_proposed_missing_data

Claude

remove_products_from_group

Claude

remove_tags_from_products

Claude

reorder_custom_columns

Claude

reply_to_missing_data_email

Claude

restore_dismissed_missing_data

Claude

restore_notifications

Claude

save_analytics_view

Claude

save_procedure_checklist

Claude

send_all_missing_data_requests

Claude

send_missing_data_follow_up

Claude

send_missing_data_request

Claude

send_task_email

Claude

send_workflow_step_email

Claude

set_data_point_defaults

Claude

snooze_missing_data

Claude

start_procedure_checklist

Claude

start_tracking_missing_data

Claude

submit_procedure_checklist

Claude

update_product_group

Claude

update_products

Claude

update_tag

Claude

update_tasks

Claude

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/scanio"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/scanio)