← TradeCatalogCONTENT HISTORY
WHAT CHANGED
Update to TradeCatalog
Snapshot Oct 29, 2026 · 12:06 UTC · version 1.3.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save TradeCatalog and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Change a supplier's TradeCatalog business details, branding, order recipients or catalogue settings, invite staff, or obtain authorized export and API setup links. Use for managing an existing supplier workspace; customer access and pricing are separate workflows.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 213
}
],
"name": "tradecatalog-workspace",
"skill_md_contents": "---\nname: tradecatalog-workspace\ndescription: Change a supplier's TradeCatalog business details, branding, order recipients or catalogue settings, invite staff, or obtain authorized export and API setup links. Use for managing an existing supplier workspace; customer access and pricing are separate workflows.\n---\n\n# TradeCatalog supplier workspace\n\nSelect the intended supplier using `list_workspaces`, then read `get_workspace` and `get_settings`. Work through the connected TradeCatalog MCP tools with the person's own membership. Settings need `branding.manage`; staff invitations and API-key controls need `staff.invite`. Owner and Admin have those permissions, while other roles can be customized. The server checks current permission and plan on every action; a role label alone does not guarantee access.\n\n## Change supplier settings\n\nRead `get_settings.settings` before `save_settings`. Its nested `settings` input requires `name`, `accentColour`, `currency`, `timezone`, `taxLabel` and `orderEmails`; copy current values for everything outside the request. `orderEmails` is the complete replacement list of up to three recipients, so preserve existing recipients when adding one and show the exact final list before review.\n\nOptional fields remain unchanged when omitted: `legalName`, `registrationNumber`, `taxNumber`, `country`, `listed`, `smartSearch`, `ordersEnabled`, `priceListDownloads`, `hideProductPhotos` and `whiteLabel`. Blank legal/registration/tax fields clear their value. Choose these controls only for the person's goal:\n\n- Business identity, colour, country and tax wording affect how the catalogue appears. A currency change relabels stored minor-unit amounts; it does not convert existing prices or agreed deals. Resolve intended currency conversion separately before changing a populated catalogue. Tax wording alone does not calculate tax.\n- `ordersEnabled: false` makes customers following the supplier prices only. Customer `ordering` overrides still apply: `can_order` remains able to order and `prices_only` remains unable. Use the customer workflow when a specific account exception is requested.\n- `priceListDownloads: false` blocks buyer CSV and PDF price-list downloads; it does not hide catalogue prices or stop ordering.\n- `listed` opts the supplier into the public directory. Do not turn it on merely to help someone find their private trade portal.\n- `smartSearch` controls natural-language catalogue search; enabling it starts indexing, so a saved setting is not proof that all products are already searchable.\n- `hideProductPhotos` and enabling `whiteLabel` require Pro. Explain an unavailable setting without starting checkout or promoting an upgrade. White-label setup can require further signed-in branding/domain work; saving the toggle alone is not evidence that a branded domain is configured.\n\nUse `open_logo_settings` when the person wants to upload a supplier logo. Return its signed-in link; that tool neither reads an image nor changes the logo. Demo workspaces do not email real recipients or appear in the directory, even when submitted settings request those outcomes.\n\n## Invite the supplier's team\n\nRead `list_staff` for current members and pending invitations. Distinguish staff workspace access from a customer's purchasing access. For a requested staff invitation, use `invite_staff` with the exact recipient `email` and an explicit `role`; omission defaults to Admin and must not be used to guess the required access.\n\nSupported roles are `owner`, `admin`, `pricing_manager`, `sales_admin`, `order_handler` and `viewer`. Only an Owner can invite another Owner. Owner and Admin work on every plan; the four specialist roles require Pro. Pricing Manager focuses on catalogue/prices, Sales Admin on assigned customers, Order Handler on processing orders, and Viewer on reading. Existing members may have customized permissions, so do not promise a full set of powers from the role name alone. The legacy `staff` value is not valid for a new invitation.\n\nThe tool sends an email after review. Reread `list_staff` and report the invitation as pending until accepted. Changing an existing staff role, custom permissions, customer-region coverage, ownership or removing staff has no MCP tool: those actions finish in the signed-in **Team** page. Do not re-invite someone as a substitute for changing their existing membership.\n\n## Export and integration handoffs\n\n- `download_products_csv` returns a signed-in product export link and needs `data.export`. `download_workspace_export` returns a full workspace export link for an Owner or Admin. The user opens these links to download; generating one does not read, download or transfer customer data to another service.\n- `open_api_key_settings` returns the signed-in API settings link for credential creation. It does not create a key. `list_api_keys` returns labels and scopes without secrets; never ask for a key in chat. OAuth is already the plugin's connection and does not need a new API key.\n- For an explicitly requested integration disconnection, resolve its current `keyId` through `list_api_keys`, then use reviewed `revoke_api_key`. Revocation stops that integration immediately; it does not revoke every key or disconnect the current OAuth connection.\n\n## Confirm and report\n\nFor mutations, show the returned confirmation card or signed-in `reviewUrl` with the exact setting, recipients or role. The person confirms there; chat text is not a substitute and the agent never calls private `decide_action`. Check `get_action_status`, then reread the relevant settings, staff invitations or API-key list after success. Stop on pending, failed or uncertain outcomes instead of repeating a write. A handoff link, saved setting, invitation sent and accepted membership are distinct states; report only what the tool and fresh read establish.\n"
}SHA-256 of public snapshot: 951ab13cacbbdcd9588a708b9a387fe565342f02c9dc7d7795dc18153f2d1cbe