Skip to main content
Glama
812,455 tools. Updated 2026-11-20 19:00

"An e-commerce platform for building online stores" matching MCP tools:

  • Real-time stock levels, exact warehouse quantities available, and backorder status for e-commerce stores. Use when verifying real-time physical warehouse stock quantities, variant availability, fulfillment method (FBA vs Merchant), and restock dates for an e-commerce product URL or SKU. Do not use for historical price comparison (use getEcommercePricing) or return policies (use getMerchantReturnPolicy).
    ConnectorNo auth
  • Search or list stores in the Partle marketplace. Use for store-led questions ("what hardware shops are in Madrid?") rather than product-led ones (use `search_products` for that). Pass no query to browse the whole catalog. Read-only. No authentication. Rate-limited to 100 requests/hour per IP. Args: query: Free-text search over store name and address. Omit to list all stores in default order. limit: Max results (1–50, default 20). Returns: A list of stores with `id`, `name`, `address`, `lat`/`lon` (when geocoded), `homepage`, `type`, and `product_count` (active listings in the store — useful for competitive-landscape sizing without a separate `search_products` round-trip). Pass `id` to `search_products(store_id=…)` to filter the product catalog by that store.
    ConnectorNo auth
  • Search or list stores in the Partle marketplace. Use for store-led questions ("what hardware shops are in Madrid?") rather than product-led ones (use `search_products` for that). Pass no query to browse the whole catalog. Read-only. No authentication. Rate-limited to 100 requests/hour per IP. Args: query: Free-text search over store name and address. Omit to list all stores in default order. limit: Max results (1–50, default 20). Returns: A list of stores with `id`, `name`, `address`, `lat`/`lon` (when geocoded), `homepage`, `type`, and `product_count` (active listings in the store — useful for competitive-landscape sizing without a separate `search_products` round-trip). Pass `id` to `search_products(store_id=…)` to filter the product catalog by that store.
    ConnectorNo auth
  • Get top-level Partle platform statistics. Use for size questions ("how big is Partle?", "how many stores does Partle cover?"). Aggregate counts only — no per-product or per-store data; use `search_products` / `search_stores` for that. Read-only. No authentication. Cheap, but rarely changes — long-running agents should cache the result. Returns: ``{"total_products": int, "total_stores": int, "description": str}``.
    ConnectorNo auth
  • Get top-level Partle platform statistics. Use for size questions ("how big is Partle?", "how many stores does Partle cover?"). Aggregate counts only — no per-product or per-store data; use `search_products` / `search_stores` for that. Read-only. No authentication. Cheap, but rarely changes — long-running agents should cache the result. Returns: ``{"total_products": int, "total_stores": int, "description": str}``.
    ConnectorNo auth
  • Returns all VAT (Value Added Tax) rates for a given EU country — standard, reduced, intermediate, and super-reduced rates where applicable, as numeric percentages. Returns { country, standard, reduced?, intermediate?, superreduced? } for supported countries, or { error, available } listing all valid codes if the country is not found. Supports 18 EU member states: PT, ES, FR, DE, IT, NL, BE, PL, SE, DK, FI, AT, IE, GR, HU, RO, CZ, HR. Use when calculating EU cross-border invoice tax, determining correct rate for e-commerce checkout by customer country, generating compliant VAT breakdowns, or any workflow requiring accurate and current EU VAT rates per jurisdiction.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Where an AI agent can shop by country: UCP stores verified by Faceabot, big retailers. Free.

  • Caelara Labs E-Commerce Intelligence: remote MCP server exposing e-commerce intelligence endpoints over streamable HTTP. Published by Caelara Labs (ops@caelaralabs.com).

  • Validates a Brazilian CPF (Cadastro de Pessoas Físicas) using the official Receita Federal checksum algorithm. Use this tool when processing Brazilian user registrations, invoices, tax forms, e-commerce orders, or any document requiring a valid Brazilian individual taxpayer number. Input must be an 11-digit string (with or without formatting). Returns whether the CPF is mathematically valid, along with the cleaned CPF. Does not verify if the CPF exists in the Receita Federal database — only validates the format and checksum.
    ConnectorNo auth
  • Validates a Brazilian CNPJ (Cadastro Nacional da Pessoa Jurídica) using the official Receita Federal checksum algorithm. Use this tool when processing Brazilian company registrations, B2B invoices, supplier onboarding, e-commerce orders, or any document requiring a valid Brazilian company taxpayer number. Input must be a 14-digit string (with or without formatting). Returns whether the CNPJ is mathematically valid, along with the cleaned CNPJ. Does not verify if the CNPJ is active in the Receita Federal database.
    ConnectorNo auth
  • List verified UCP storefronts across every platform, best-evidenced first. Use when the user wants to browse stores — e.g., "what stores can I shop at?" or "show me Wix stores". To find stores that sell something, prefer search-all. Each store carries what we have actually observed about it, not what it claims: - `transactable` — declares checkout and we have read its catalogue - `catalogued` — we have read its catalogue - `resolvable` — its endpoint resolves, we have not probed it yet - `declared` — a valid profile, nothing observed beyond it Filter by `platform` (shopify, wix, woocommerce, bigcommerce, shopware…). `category` narrows to the smaller set of deeply audited stores (see list-categories), so leave it out unless the user asks for a category. Developer previews and staging hosts are not listed.
    ConnectorNo auth
  • Check whether one or more dm-drogeriemarkt products are available in one or more specific stores right now. USE WHEN: you need to know if one or more products can currently be bought in one or more particular physical stores. INPUT: one to five storeIds and one to ten DANs (dm product numbers). OUTPUT: for each requested DAN, whether it was found and a status per requested storeId - VERFUEGBAR (available, includes current stockLevel), NICHT_VERFUEGBAR (not available in this store right now), NUR_ONLINE (this product is not carried in ANY dm store, not just this one), PRODUKT_UNBEKANNT (DAN not found), or STORE_UNBEKANNT (storeId does not exist in our system). IMPORTANT: NUR_ONLINE means the product itself is never sold in physical dm stores - it will be the same result for every store. Do not check other or nearby stores for that product; tell the customer it is online-only right away. IMPORTANT: storeIds MUST come from the findNearbyStores tool - call it first to resolve the storeId(s) for a location. Never invent, guess, or otherwise make up a storeId yourself; a made-up storeId will come back as STORE_UNBEKANNT instead of a real availability answer. IMPORTANT: if a customer asks about availability for several products, pass ALL of their DANs (up to 10) into this single call. Never assume, infer, or extrapolate the availability of a product you have not included in a call and gotten a result for - not even from a similar or already-checked product, and not even for "usually available" items. When reporting back, state the result for every single product individually (e.g. one line per product) - never collapse multiple products into one summary statement such as "all of them are available". TIP: if a product's result is NUR_ONLINE, or it is NICHT_VERFUEGBAR and you already know from an earlier product lookup that it is available online, suggest buying it online instead and include a link to the product page if you have one. NOT FOR: click & collect / express pickup or same-day delivery eligibility (not covered by this tool), or repeatedly polling a store's stock over time. ERRORS: validation error if any DAN is invalid, dans is empty, more than 10 dans are given, storeIds is empty, or more than 5 storeIds are given.
    ConnectorNo auth
  • Searches stores by name and returns the matching stores' identity only — store_id, name, country_code, website domain and GotCashback store page url — without cashback rates or gift cards. Use it when the user wants to know whether GotCashback covers a store, in which countries a store is listed, or when you need a store_id for the account tools (toggle_favorite_store, set_store_alert). For any question about cashback rates or gift card discounts call get_cashback_rates_by_store_name or get_gift_cards_by_store_name directly instead — they search by name themselves, so this tool is not a required first step. Returns matches best first; empty when nothing matched. When presenting stores, include each store's 'url' as a clickable link (and 'gift_cards_url' when present).
    ConnectorNo auth
  • Searches stores by name and returns the matching stores' identity only — store_id, name, country_code, website domain and GotCashback store page url — without cashback rates or gift cards. Use it when the user wants to know whether GotCashback covers a store, in which countries a store is listed, or when you need a store_id for the account tools (toggle_favorite_store, set_store_alert). For any question about cashback rates or gift card discounts call get_cashback_rates_by_store_name or get_gift_cards_by_store_name directly instead — they search by name themselves, so this tool is not a required first step. Returns matches best first; empty when nothing matched. When presenting stores, include each store's 'url' as a clickable link (and 'gift_cards_url' when present).
    ConnectorNo auth
  • How this Aevia connection works, plus playbooks for results, reports, systems. Returns a skill's playbook as the result; takes no action itself. A playbook is step-by-step guidance for a multi-step job, too long for a description. `connector_guide` covers how this connection works: workspaces, refs, finding data, the library, building, calculating and failures. `assessment_interpretation` covers reading and comparing results: what an indicator result is and is not, a figure's anchors, functional-unit equivalence and comparison discipline. `report_writing` covers writing results up as a document, from a screening note to an ISO 14044 study. `product_system_authoring` covers building a new product system with `lca_compose_assembly` / `lca_compose_linked`: build order, which of the two fits, failure modes, and tagging life-cycle phases. A loaded playbook stays in context; one load per session suffices. Skills are gated on what the token can call; an unavailable request returns the available list.
    ConnectorAPI key
  • Files a concierge switch request with the complete contract data in one call. Intended for autonomous agents that already hold the user's full profile, IBAN and a standing authorization; in a conversation with a person, start-booking opens a form in which the user enters these data. Commerce for Agents stores the request encrypted and an operator submits the contract application to the provider; the user receives a confirmation email at once and the provider's contract documents later. There is no self-service checkout link. Input: the `ref` of the chosen offer plus the contract data. Postal code and city come from the comparison; previousProvider, previousCustomerNumber and meterNumber are printed on the last energy bill. `consent: true` attests that the user explicitly agreed to (1) Commerce for Agents submitting the contract on their behalf, (2) the SEPA direct-debit mandate for the given IBAN and (3) the privacy policy at commerceforagents.com/privacy, either by an explicit yes in the conversation or by a standing authorization given to the agent. The response contains nextSteps for the user.
    Connector
    Destructive
    No auth
  • Saves redirect mappings (old URL -> new URL) for a site migration, tied to the source property A and target property B they move traffic between. These back the Migration Compare workflow: use compare_migration for the before/after performance read, and these mappings to record which old URL became which new one. Pass `label` to keep several migrations apart on one account. Rows are APPENDED, never deduplicated against what is already stored, so re-sending the same list stores it twice; clear a set first with delete_migration_redirects if you are re-uploading. An account stores at most 200,000 mappings in total.
    ConnectorOAuth
  • Checks whether a name/handle is available on 70+ platforms at once: domain names (.com, .fr, .io, .app…), social networks (Instagram, TikTok, X, YouTube…), creative and dev platforms (GitHub, Behance…), e-commerce, freelance, gaming and company registries. Takes 5-15 s on first call (results cached 10 min). Statuses: available, likely_available, taken, manual (cannot be checked automatically), unknown (check failed). Never present manual/unknown results as available. Available domains come with a registration link. Each call is a full live search: to compare many name ideas, first use check_domains (up to 10 names per call), then check_name only on the shortlist.
    ConnectorNo auth
  • Report BUILDING PERMITS and other construction acts on a property, around it, or in an area (gradbeno dovoljenje, uporabno dovoljenje, inspekcija, legalizacija). INPUT: a property `ref` or a parcel `ref` (from find_parcels / find_by_cadastral_ref — an unbuilt plot), OR an `area` from find_area. Optional `radius_m` (default 300, max 2000) and `since_year` (2015 or later). READ: `subject` — `parcel` answers for that parcel alone. `on_property` for acts on the property's own parcel; `nearby.by_class` for acts within `radius_m`; `municipality.years` for the local rate beside `national_acts_per_1000_addresses`. READ: `act_class` on every row. `build_permit` = work ALLOWED, `use_permit` = building FINISHED, `start_notice` = work STARTED. READ: `is_adverse`. `enforcement` (inspection proceedings) and `legalisation` (built first, legalised after) are FINDINGS against a property, not permissions. READ: `freshness.is_stale` and `freshness.age_days` before saying nothing new was filed. NEVER: add classes into one total, or read `n_pending` as a construction pipeline — most pending acts are `enforcement`, i.e. open proceedings. NEVER: read an empty `on_property` as "never permitted" — old parcel numbers are lost (`freshness.share_keys_resolved_to_parcel`), so a parcel's history is a floor. THEN: `property_land` for the designated use — nothing here is zoning. `neighbourhood` for what stands around it.
    ConnectorOAuth
  • Get a link to upload a recording that's over 2 MB and isn't already online, up to 100 MB. PUT the file's bytes to upload_url (e.g. curl -T memo.m4a '<upload_url>'), then pass upload_id to transcribe_audio or add_voice_note. For a smaller file, pass audio_base64 to those tools instead; for one already online, audio_url. The link works for 15 minutes; the upload_id for a day. The recording is deleted once it's transcribed.
    ConnectorOAuth
  • **\[Store Products\]** **\[What it does\]** Starts a whole-store price-sync task for one to 20 owned stores. Product BFF applies each store's currently enabled Pricing Rule to all eligible mapped products. **\[When to use\]** Use when the merchant explicitly wants to reapply the enabled Pricing Rule across complete stores. **\[When not to use\]** For one exact product or variant, use `update_managed_store_product`. For pre-publish products, use `update_pre_publish_product_price`. This Tool does not accept product filters, variant filters, fixed/percentage adjustment inputs, or Pricing Rule changes. **\[How to use\]** Copy the complete `dsers_store_ids` selection from `list_stores`. The preflight verifies store ownership, an enabled Pricing Rule, and no conflicting active task; it does not calculate a per-product price preview. The write creates an async task; after confirmation, poll `get_job_status` with the returned `task_type` and `task_id`; its `result` contains the current and final per-store progress. If task creation is uncertain, check status instead of creating another task. **\[Side effects\]** May change buyer-visible prices for every eligible mapped product in each selected store. **\[Confirmation\]** Required, never skippable: show the exact stores and explain that their enabled Pricing Rules apply store-wide.
    Connector
    Destructive
    OAuth
  • Saves redirect mappings (old URL -> new URL) for a site migration, tied to the source property A and target property B they move traffic between. These back the Migration Compare workflow: use compare_migration for the before/after performance read, and these mappings to record which old URL became which new one. Pass `label` to keep several migrations apart on one account. Rows are APPENDED, never deduplicated against what is already stored, so re-sending the same list stores it twice; clear a set first with delete_migration_redirects if you are re-uploading. An account stores at most 200,000 mappings in total.
    ConnectorAPI key
  • List the tenant's warehouses (id, name, code, internal/external type, replenishment mode, and any custom field values set on the warehouse — customFields, keyed by fieldName; see list_custom_fields with entity=warehouse). Use the ids with set_inventory_levels / set_inventory_policy / transfer tools. Each warehouse also lists its stores (storeId, name, code): stores and warehouses are DISTINCT entities with different ids, and a warehouse's companion store shares its name, so when a store id is needed (import_historical_sales_orders, create_import_session, or the REST POST /api/v1/sales-orders/import endpoint) answer with stores[].storeId — the warehouse id is never a valid store id. Tenants get a Main warehouse at signup; create more with create_warehouse. Existing array shape is preserved. Omit limit for a complete list up to 100 warehouses; larger lists require explicit limit/offset. For explicit pages, advance offset by limit until a short page. Nested stores are capped at 1000 per response; use warehouseId with storeLimit/storeOffset to page one warehouse's stores in the same way. Set includeStores=false to discover warehouse ids without loading nested stores. Use includeCustomFields=false or customFieldNames to narrow large payloads.
    ConnectorOAuth