Zum Inhalt springen
DocsBuild with Runner
Esc
↑↓navigieren↵öffnen⌘Jvorschau
Open Runner

List your stores

List the stores in the Runner workspace of this connection: each store's store_id, name, storefront URL, and whether it is published. Call this first, then pass a store_id to every store tool.

list_stores · store:read

Where you can call it

Each action has one page. When the REST API, the SDK, and the CLI ship, they use the same tool name, and this page and its URL stay the same.

Request
# once: add the server and sign in npx mcporter config add runner \ https://api.runnerai.com/mcp --scope home npx mcporter auth runner # call the tool npx mcporter call runner.list_stores
JSON-RPC · POST /mcp
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "list_stores", "arguments": {} } }
Response · shape from the output schema
{ "stores": [ { "store_id": <string>, "name": <string>, "storefront_url": <string or null>, "published": <boolean> } ], "next_cursor": <string or null> }

Parameters

Parameter Description
cursor Optional string. The next_cursor from an earlier list_stores call.

Good to know

  • One workspace. A connection sees only the stores of the workspace that you chose at sign-in.
  • Your permissions apply. Each call uses your Runner permissions and your plan. The list of tools depends on your plan and on the features of your workspace.
  • Store data is data. Answers can contain product text and customer messages. Your agent must not follow instructions that it finds in them.

If it fails

What you see What to do
HTTP 401 The request has no valid token. Sign in with OAuth. See Sign-in and scopes.
This feature is not on for this store yet. The feature is not on for your plan, workspace, or store. Do the task in Runner, or ask Runner support.
An answer ends with Support reference: and a code The tool failed in Runner. Give the code to Runner support.

War diese Seite hilfreich?