Business Bridge MCP Server

connect_shopify

Establishes a connection to a Shopify store using API credentials to enable querying products, orders, and inventory.

Instructions

Shopify-Store verbinden.

Richtet eine Verbindung zu einem Shopify-Store ein. Danach können Produkte, Bestellungen und Inventar abgefragt werden.

Args: connector_name: Eindeutiger Name für diese Verbindung (z.B. "mein-shop") store_url: Shopify Store URL (z.B. "https://mein-shop.myshopify.com") api_key: Shopify Admin API Access Token

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "connector_name": "<connector_name>",
      "store_url": "<store_url>",
      "api_key": "<api_key>"
    },
    "name": "connect_shopify"
  }
}

Input Schema

Name	Required	Description	Default
`connector_name`	Yes
`store_url`	Yes
`api_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 24, 2026

TDQS

A4.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It describes the action of setting up a connection but does not disclose details like whether it overwrites existing connections, performs validation, or has rate limits. The behavior is minimally transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with two sentences plus a parameter list, front-loading the main purpose. Every part is necessary with no redundant words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 3 required parameters, no output schema, and no annotations, the description adequately explains the purpose and parameters. It mentions the follow-up actions (querying products, orders, inventory), but lacks details on success/error handling or connection lifecycle, which are minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no descriptions for its properties (0% coverage). The description adds meaning by explaining connector_name as a unique name, store_url as the Shopify store URL, and api_key as the access token, going beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('verbinden' - connect) and resource ('Shopify-Store'), and clearly states the action of establishing a connection. It distinguishes from sibling tools like connect_calendly or connect_wordpress by naming Shopify explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by stating that after connection, products, orders, and inventory can be queried, indicating this tool is a prerequisite for other Shopify tools. However, it does not explicitly state when not to use or provide alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server