Skip to main content
Glama

Store: Start Connection

start_store_connection
Idempotent

[Store or Supplier Account] [What it does] Installs one selected application if needed and generates its external authorization link. It supports seller applications for a new store connection and only AliExpress or Alibaba.com for adding a supplier account. A returned link does not mean the store or supplier account is connected. [When to use] Use after the user selects a seller application, or explicitly asks to add an AliExpress or Alibaba.com supplier account. [When not to use] For an existing seller store needing reconnection, use start_store_reauthorization. Other supplier applications cannot add accounts through this Tool. [How to use] Provide exactly one identifier: copy recommend_apps_to_install.recommendations[].app_id into sales_channel_id for a seller application, or into supplier_platform_id only when that recommendation is AliExpress or Alibaba.com. An already-installed seller ID may also come from list_stores.stores[].sales_channel_id; an installed supplier ID may come from list_stores.supplier_apps[].supplier_platform_id. Never send both IDs. country is seller-only and should be passed only when that seller platform requires a country-specific flow. A successful response returns app_type, the matching sales_channel_id or supplier_platform_id, app_name, a validated HTTPS authorization_url, and generated_at; external authorization is still pending. The upstream platform controls URL lifetime and reuse. If the outcome is unresolved, verify seller connections or supplier accounts in DSers before retrying. [Side effects] May install the selected seller, AliExpress, or Alibaba.com application. [Confirmation] Requires explicit, non-skippable confirmation; show the selected application and country choice first. [Follow-up] Give the returned authorization_url to the user to complete authorization on the platform, then verify the new connection in DSers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_store_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoOptional seller-platform country forwarded to authorization. Use only when the selected seller app requires it, such as a country-specific TikTok flow. Do not provide it for supplier accounts.
sales_channel_idNoSeller application ID returned by recommend_apps_to_install, or list_stores stores[].sales_channel_id for an installed platform. Provide exactly one of sales_channel_id and supplier_platform_id.
supplier_platform_idNoAliExpress or Alibaba.com supplier application ID returned by recommend_apps_to_install, or list_stores supplier_apps[].supplier_platform_id. Other supplier applications are rejected. Provide exactly one of supplier_platform_id and sales_channel_id.

Output Schema

NameRequiredDescriptionDefault
app_nameYesSelected application name
app_typeYesSelected application type: seller or supplier
generated_atYesRFC3339 time when the authorization URL was generated
sales_channel_idNoSelected seller application ID as a decimal string; present only for seller connections
authorization_urlYesExternal platform URL the user must open to authorize the new store
supplier_platform_idNoSelected AliExpress or Alibaba.com application ID as a decimal string; present only for supplier connections
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare non-read-only, open-world, idempotent, non-destructive behavior, and the description reinforces this well by disclosing that the tool may install an application, requires non-skippable confirmation, and that a returned link does not mean the account is connected. It also notes the upstream platform controls URL lifetime and reuse, which is useful context beyond the annotations.

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

Conciseness4/5

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

The labeled sections (What it does, When to use, When not to use, How to use, Side effects, Confirmation, Follow-up) make it easy to scan and front-load the key routing information. It is somewhat long and repeats the mutually exclusive ID rule already stated in the schema, but no sentence is out of place.

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

Completeness5/5

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

With an output schema and annotations already covering the safety profile, the description is complete: it covers invocation rules, side effects, confirmation requirements, response fields, and the required follow-up to hand the authorization_url back to the user and verify in DSers.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents the three parameters and the exactly-one-ID rule. The description adds some value by tracing where each ID comes from (recommend_apps_to_install, list_stores) and clarifying that country applies only to seller flows, but this largely restates what the schema descriptions already say.

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 states a specific verb and object: installs one selected application and generates its external authorization link. It also scopes the tool to seller applications for new connections and AliExpress/Alibaba.com supplier accounts, and explicitly distinguishes itself from start_store_reauthorization for reconnection cases.

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

Usage Guidelines5/5

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

It has explicit when-to-use (user selects a seller application or asks to add an AliExpress/Alibaba.com supplier account) and when-not-to-use (reconnection goes to start_store_reauthorization; other supplier apps are unsupported). The alternative is named along with the condition that selects it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.