Tools appear in bold, as the assistant names them.

Changes take effect as soon as a release is deployed. Fully quit and reopen your app, or start a new session, so it picks up new and changed tools.

You can see which release is running by opening https://mcp.ipaas.com/health in a browser. It shows the date the current release was deployed.

This is a beta. Features may be added, removed or changed. Anything that removes or changes existing behaviour is listed under Breaking changes.

resync_record and resync_batch now tell you whether each record was delivered, not just that the sync started. Each record comes back as delivered, not delivered with the reason, or still running.

When a record didn't arrive, the result says which case it is. Either the destination was reached and declined the record, which usually means a mapping collection's filter, or the destination was never reached, which on a sync into iPaaS.com often means the source had nothing to send. Neither case puts anything in the error queue.

list_transactions can now combine filters, such as a customer and a type. A modified-since date still can't be combined with another filter, because the platform would apply the date comparison to the other field too and return other customers' transactions. The tool refuses that combination and says why.

Finding the error for a sync. An error is found by the ID of the job that produced it (the hook ID a resync returns), not by the sync's tracking ID. The tools used to suggest the tracking ID, which never matches an error, so the queue looked empty. They now point to the job ID.

check_hook_completion now judges delivery at the destination. For a record coming into iPaaS.com it used to read the size of what was fetched from the source, so a run that wrote nothing into iPaaS.com could show as delivered.

check_hook_completion no longer reports "pending" indefinitely for a record coming into iPaaS.com. It reads the direction from the job itself, so you don't need to give one.

enable_webhook now reads every webhook scope. On companies with several connectors, real scopes beyond the first page were refused as if they didn't exist.

enable_webhook now matches scope names exactly when it checks whether a webhook already exists. Similar names, such as shipping/method/created and shippingmethod/created, were treated as the same, so the second couldn't be enabled. If what you type matches more than one scope, it asks which one you mean.

Field maps. Some business values, such as currency, sales channel, committed stock, reorder settings, consent and lifecycle, don't have a native field in iPaaS.com yet. Many companies already keep them in custom fields under their own names. A field map tells the MCP which custom field holds which value, so the business reports can use them.

enable_webhook and disable_webhook. Start or stop sending a scope's changes to a destination system. Enabling creates the webhook and refuses to create a second one for the same scope and destination, since a duplicate makes a record fire twice. Disabling deletes the webhook for good, so enabling it again creates a new one with a new ID. Both preview first.

explain_subscription_setup. Ask the assistant to connect a system, such as "set up Shopify". It can't do it, because setup needs that system's own credentials, which shouldn't pass through a chat. It now says so plainly and gives you the installation guide for that integration, or points you to support@ipaas.com when there isn't one.

check_inventory_health no longer includes discontinued products in any of its alert lists. Before, it left them out of some lists and not others.

The field map tools now say honestly which values change a report today and which are saved for later, instead of implying that every answer is used.

Tools now reject arguments they don't recognise. Before, a tool silently dropped an argument it didn't know and gave you a result worked out from the rest. For example, a filter sent under an old name returned the whole unfiltered list, reported as if it had been filtered. Now the tool stops and tells you which argument it doesn't recognise (the message includes "Unrecognized key").

What to do: if you have saved prompts, scripts or custom clients that pass tool arguments, check each argument's name against the tool's current definition and remove any that no longer exist.

dismiss_errors. Clear an error from the queue once its cause is dealt with, or move it to another status. It shows a preview first, works on up to 25 at a time, and doesn't fix or retry anything.

describe_write_schema. Shows what a write needs before you try it: the required fields, the allowed values, and fields the platform accepts but ignores. It saves the trial and error of guessing at a request.

create_catalog_records. Create up to 25 products or other catalog records in one call. Every record is checked before any is sent.

get_active_tenant now says whether your connection is using an API key or a sign-in token, and warns you before a sign-in token expires. Sign-in tokens work and then suddenly stop with a 401, so you should use an API key.

Previews catch more mistakes. A preview now checks the whole request, including fields nested inside lines, addresses and variants, and flags any field the platform would silently ignore. It flags a variant that repeats an option, and it warns when an update would clear a value the record currently holds.

Tools that can't work now say so. Some writes, such as to transaction lines, addresses, notes, payments and taxes, aren't available in the platform's API yet (they need to be written at the parent level). Tools used to fail in confusing ways. They now stop immediately and suggest the alternative.

Sessions are tied to the key that opened them. A connection can no longer be used without a key, or by someone else's key, once it has been opened.

Gift card activity now requires the resulting balance. An activity records why a balance changed, and does not change the balance itself. The tool used to send back the old balance, so redeeming 10 from a 50 card could record the activity but leave the balance at 50. You now state the balance the card should have.

Resync warns about records that move with a parent. A transaction line travels with its transaction, and a variant with its product. Resyncing one on its own could report a clean run and send nothing. The tool now says so.

Disabling a mapping collection that has children now shows the full ordered plan and works from the deepest child up. It refuses to disable children you didn't ask about unless you say so, and the result includes the reverse order so you can undo it.

summarize_sales_performance counts only real orders. It used to count quotes, invoices and cancelled orders as orders and add their totals to revenue, and returns reduced it. It also now reads every page of locations.

check_feature_support no longer says "unsupported" for integrations that describe their support in their own words. It now decides from the data type itself.

Transaction types and statuses now come from the platform's own lookup tables. This adds the tenth type, Fulfillment, which couldn't be filtered for before.

find_mapping_collections and related searches now read every page. A company with hundreds of collections could be told "no match" about one that existed.

Copying a mapping (propagate_mappings) now sends the source field's ID. Plain field mappings used to fail while the copy reported success.

Updating a record that has categories (a product, customer or company) no longer fails because of how the category was sent back. Writes to variant units are now refused with an explanation.

External ID tools now work with every table the platform offers, not just five.

Poll events are now read correctly, so get_inbound_delivery sees the poll events you have configured.

The first status after a resync no longer reads as an anomaly. It is the receiver's normal acknowledgement.

Records come back exactly as the platform sent them. The generic readers used to reformat numbers, so 48.0 came back as 48.

Custom field searches read the full list, and a duplicate name is checked exactly. A company with hundreds of definitions could previously miss a name that was already taken.

Several tools no longer send arguments the platform ignores, which had made some searches report "none" about data that was there.

Data tools for Products, Customers, Transactions, Gift Cards, Employees and Messages and Images. These can read and, with the right permissions, create, update, delete and reactivate records, always with a preview first.

Integration tools for connected systems, mapping and translation collections, formulas, errors, logs, webhooks, events and polling.

Fixing failed syncs: diagnose_error, resync_record, resync_batch, check_records_landed and check_hook_completion.

Business reports for sales performance, inventory health, stuck orders and gift card liability, with plain-language results.

Choosing your tools: domains and shortcuts in the server URL, and a business style for results.

Reference and formula tools: data-type matching, the data model, help article search, formula validation and preview, and the platform API's own documentation.