← WebMCP Directory

jour-cards.com

jour-cards.com

live Unverified (seed import) Commerce 16 tools imperative implementation

Jour Cards Store is an online shop selling digital gift cards for iTunes, Xbox, Google Play, Amazon and more, payable with Bitcoin and other crypto.

First seen 2026-10-12 · Last seen 2026-10-12 · Source: webmcp.com

Answer 6 · Act 8 · Transact 2 · Score: Not yet scored

Tool inspector

ExecuteWixAPI

act imperative

Run JavaScript against the Wix REST API on site "Jour Cards Store" (https://www.jour-cards.com//_api/mcp?withSkills=true), on the visitor's behalf. The code runs in a sandbox and you get back whatever it returns. PREFER THIS TOOL OVER CallWixSiteAPI. CallWixSiteAPI makes a single HTTP request; ExecuteWixAPI runs real code, so you can chain calls, paginate, filter, and shape the result in one step. Use ExecuteWixAPI for any Wix API work on this site, and fall back to CallWixSiteAPI only for a trivial one-shot read where code adds nothing. DO A WHOLE RECIPE IN ONE CALL. When a task needs several requests — e.g. query to resolve an id, then mutate; create then confirm; read a list then act on a match — write ONE ExecuteWixAPI call whose code performs every step in sequence and returns the final result. Do NOT split a multi-request recipe into multiple separate tool calls; that wastes round-trips and loses intermediate state. If a recipe from the docs lists steps 1..N, the code should run steps 1..N. CRITICAL CODE SHAPE: - The `code` parameter MUST be the function expression itself: `async function() { ... }` or `async () => { ... }`. - Do NOT send a script body like `const result = await ...; return result;`. - Do NOT call the function yourself. The tool calls it for you. - Put all `const`, `await`, and `return` statements inside the function body. Do not rely on memory for Wix API endpoints, methods, schemas, or request bodies. Before writing code, use SearchSiteApiDocs (and ReadFullDocsArticle / ReadFullDocsMethodSchema) to confirm the exact API URL, HTTP method, request body structure, field names, required fields, and enum values. The URL usually starts with `https://www.wixapis.com`. Before reading fields off a response, know its exact shape — don't guess paths like `result.id` when it may be `result.results[0].item.id`. Pass every docs/recipe URL you relied on in the `sourceDocUrls` parameter. Authentication: pass the `visitorToken` parameter (from GenerateVisit…

Input schema

PropertyTypeRequiredDescription
code string yes JavaScript async function expression to execute against the Wix REST API. The value must be the function itself, for example `async function() { ... }` or `async () => { ... }`, not a script body and not an invoked function. Return the final answer from inside the function. Do not write top-level `const`, top-level `await`, or top-level `return` outside the function body. Use `wix.request({ method, url, body })` for Wix API calls. Every call runs against the current visitor site; do not set `scope`, `siteId`, or auth headers. Full Wix API URLs and paths starting with `/` are supported. Wix REST API page size limits vary — use 100 as a safe default unless the method schema (via SearchWixAPISpec) confirms a higher limit is supported. For cursor-based APIs, pass the next cursor as `cursorPaging: { limit: 100, cursor: pagingMetadata.cursors.next }` — not inside `paging`. Check the method schema to confirm whether the API uses `paging` (offset-based) or `cursorPaging` (cursor-based) before paginating.
reason string yes One sentence explaining the original user request and why you are executing code to complete it.
hasMutations boolean yes Whether this code creates, updates, deletes, publishes, imports, uploads, or otherwise mutates site data on the visitor’s behalf. Set this to true for create/update/delete/bulk create/import/upload calls even if the reason is inspection, verification, or response-shape discovery. Read-only GET/query/list/search calls can use false.
sourceDocUrls array yes The URLs of the documentation, recipes, API articles, or schema sources where you confirmed the Wix REST endpoints, HTTP methods, request body shapes, auth contexts, and required fields used by this code. Include every docs/schema source needed for the endpoints and request shapes used in the code. MAKE SURE THE ENDPOINT URLS AND REQUEST SHAPES ARE REALLY THERE AND YOU ARE NOT GUESSING THEM !!! Each value must be a valid URL like: - https://dev.wix.com/docs/api-reference/... (REST API reference docs) Use ["user-provided"] if the user gave you all endpoint and request details directly. Use ["other"] ONLY IF YOU HAVE A VERY GOOD REASON TO DO SO
Raw JSON schema
{
  "type": "object",
  "properties": {
    "code": {
      "type": "string",
      "description": "JavaScript async function expression to execute against the Wix REST API. The value must be the function itself, for example `async function() { ... }` or `async () => { ... }`, not a script body and not an invoked function. Return the final answer from inside the function. Do not write top-level `const`, top-level `await`, or top-level `return` outside the function body. Use `wix.request({ method, url, body })` for Wix API calls. Every call runs against the current visitor site; do not set `scope`, `siteId`, or auth headers. Full Wix API URLs and paths starting with `/` are supported. Wix REST API page size limits vary — use 100 as a safe default unless the method schema (via SearchWixAPISpec) confirms a higher limit is supported. For cursor-based APIs, pass the next cursor as `cursorPaging: { limit: 100, cursor: pagingMetadata.cursors.next }` — not inside `paging`. Check the method schema to confirm whether the API uses `paging` (offset-based) or `cursorPaging` (cursor-based) before paginating."
    },
    "reason": {
      "type": "string",
      "description": "One sentence explaining the original user request and why you are executing code to complete it."
    },
    "hasMutations": {
      "type": "boolean",
      "description": "Whether this code creates, updates, deletes, publishes, imports, uploads, or otherwise mutates site data on the visitor’s behalf. Set this to true for create/update/delete/bulk create/import/upload calls even if the reason is inspection, verification, or response-shape discovery. Read-only GET/query/list/search calls can use false."
    },
    "sourceDocUrls": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The URLs of the documentation, recipes, API articles, or schema sources where you confirmed the Wix REST endpoints, HTTP methods, request body shapes, auth contexts, and required fields used by this code.\nInclude every docs/schema source needed for the endpoints and request shapes used in the code.\nMAKE SURE THE ENDPOINT URLS AND REQUEST SHAPES ARE REALLY THERE AND YOU ARE NOT GUESSING THEM !!!\nEach value must be a valid URL like:\n- https://dev.wix.com/docs/api-reference/... (REST API reference docs)\nUse [\"user-provided\"] if the user gave you all endpoint and request details directly.\nUse [\"other\"] ONLY IF YOU HAVE A VERY GOOD REASON TO DO SO"
    }
  },
  "required": [
    "code",
    "reason",
    "hasMutations",
    "sourceDocUrls"
  ]
}

Similar websites

4over4.com

4over4.com

4OVER4.COM prints 1,000+ custom products on 60+ paper stocks in Queens, with same-day shipping on most orders and 150,000+ businesses served since 1999.

live Unverified Commerce Transact tools
73 tools A24 / Act48 / T1 Not yet scored Seen 2026-10-12
go_to_product go_to_category go_home search_site open_ai_mode
Inspect tools
camdentools.com

camdentools.com

Construction tools and equipment

live Unverified Commerce
50 tools A36 / Act14 / T0 Not yet scored Seen 2026-10-12
cart_add_item cart_apply_promo cart_clear cart_get cart_remove_item
Inspect tools
birmakine.com

birmakine.com

Bir Makine — Turkish marketplace for industrial machinery; browse current listings and find machines that fit your needs.

live Unverified Commerce
44 tools A3 / Act41 / T0 Not yet scored Seen 2026-10-12
search_listings scan_images_c2pa inspect_image_c2pa ilan_ara ilan_detay
Inspect tools
vaanzari.com

vaanzari.com

Explore handcrafted Banarasi sarees from Vaanzari, with artisan provenance, woven traditions and thoughtful customer care in India and worldwide.

live Unverified Commerce Transact tools
37 tools A17 / Act15 / T5 Not yet scored Seen 2026-10-12
scan_images_c2pa inspect_image_c2pa search-sarees get-saree compare-sarees
Inspect tools

Related on Influzer