de en es ja ko ru zh

sellercloud-mcp

Name: sellercloud-mcp
Author: alveyautomation

by alveyautomation

Overview Schema Source Related Servers Discussions Admin

Python

Remote

sellercloud-mcp

SellerCloud初のModel Context Protocolサーバー。Claudeをカタログ、在庫、注文、チャネルリスティングに接続し、5分で読み取り専用の連携を実現します。

License: MIT Python 3.10+ MCP

このプロジェクトの目的

SellerCloudには公開SDKがありません。REST APIは十分に文書化されていますが、ブランド化されておらず、自動化を行うチームは毎回同じ認証やページネーションの処理をゼロから記述することになります。

Claude（またはMCP対応のAIアシスタント）を日常的なEC業務に使用する場合、このギャップが「今日の注文を要約して」がすぐに使えるか、カスタム統合が必要になるかの分かれ目となります。

sellercloud-mcpはこのギャップを埋めます。これは、7つの読み取り専用SellerCloudエンドポイントをMCPクライアントに公開する、軽量でテスト済みのMITライセンスMCPサーバーです。長年にわたるEC自動化の経験に基づいて構築されています。

Related MCP server: keycrm-mcp

できること

このサーバーをClaude Code、Claude Desktop、または任意のMCPホストに接続し、以下のような質問を投げかけることができます：

「WIDGETを含むSKUを検索して、在庫レベルを表示して。」
「昨日、すべてのマーケットプレイスで何件の注文が出荷されましたか？チャネルごとにグループ化して。」
「注文番号100001を取得して、どの明細が出荷されたか教えて。」
「会社ID 9001に設定されているチャネルを一覧表示し、どれがアクティブか教えて。」
「SKU ACME-001について、すべてのチャネルリスティングの価格を比較して。」

Claudeが直接カタログを読み取ります。コピー＆ペーストやスプレッドシート、カスタムパイプラインは不要です。

ツール (v0.1, すべて読み取り専用)

ツール	機能
`sellercloud_search_products`	カタログの全文検索（名前、SKU、属性）。
`sellercloud_get_product`	正確なSKUで製品を1つ取得。
`sellercloud_search_orders`	指定期間の注文を一覧表示（会社でスコープ指定可能）。
`sellercloud_get_order`	IDで注文を1つ取得（明細を含む）。
`sellercloud_get_inventory`	SKUごとの現在の手持ち/予約/発注済み数量。
`sellercloud_list_channels`	設定済みのマーケットプレイス/チャネルフィードの一覧。
`sellercloud_get_channel_listing`	SKUごとのチャネル別リスティング詳細。

書き込みエンドポイント（注文作成、在庫更新、チャネル変更のプッシュ）は、意図的にv0.1には含まれていません。読み取り専用の操作性が安定した後、v0.2で計画されています。

インストール

pip install sellercloud-mcp

v0.1はこのリポジトリから提供されます。PyPIへの公開は保留中です。現時点では pip install git+https://github.com/alveyautomation/sellercloud-mcp でインストールするか、クローンしてローカルで pip install -e . を実行してください。

認証情報の構成

サーバーは環境変数からすべてを読み取ります。.env.example を .env にコピーし、テナント情報を入力してください：

SELLERCLOUD_API_URL=https://your-team.api.sellercloud.com/rest/
SELLERCLOUD_USERNAME=your-username
SELLERCLOUD_PASSWORD=your-password
SELLERCLOUD_DEFAULT_COMPANY_ID=        # optional fallback
SELLERCLOUD_HTTP_TIMEOUT=60            # optional, seconds
SELLERCLOUD_MAX_RETRIES=3              # optional

読み取り専用のSellerCloudアカウントを使用してください。 v0.1は GET エンドポイントのみを呼び出しますが、防御的プログラミングの観点から、何も変更できない専用ユーザーをサーバーに割り当てるべきです。書き込みツールを備えたv0.2がリリースされたら、その時に権限をアップグレードしてください。逆の順序で行わないでください。

Claude Codeへの接続

~/.claude/claude_code_config.json（またはプロジェクトのMCP設定）に追加します：

{
  "mcpServers": {
    "sellercloud": {
      "command": "sellercloud-mcp",
      "env": {
        "SELLERCLOUD_API_URL": "https://your-team.api.sellercloud.com/rest/",
        "SELLERCLOUD_USERNAME": "your-username",
        "SELLERCLOUD_PASSWORD": "your-password",
        "SELLERCLOUD_DEFAULT_COMPANY_ID": "9001"
      }
    }
  }
}

Claude Codeを再起動します。新しいセッションで7つの sellercloud_* ツールが表示されます。

Claude Desktopへの接続

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) または %APPDATA%\Claude\claude_desktop_config.json (Windows) を編集し、上記と同じ mcpServers ブロックを追加します。デスクトップアプリを再起動してください。

ツールリファレンス

すべてのツールはJSONエンベロープを返します：

{ "ok": true,  "data": { ... } }
{ "ok": false, "error": "human-readable message" }

`sellercloud_search_products`

sellercloud_search_products(
    query: str,                          # required
    company_id: int | None = None,       # falls back to default if unset
    page: int = 1,
    page_size: int = 50,                 # capped at 50 by SellerCloud
)

レスポンス例：

{
  "ok": true,
  "data": {
    "items": [
      { "ID": "ACME-WIDGET-001", "ProductName": "Acme Widget, Standard", "Price": 29.99 }
    ],
    "total": 1,
    "page": 1,
    "page_size": 50
  }
}

`sellercloud_get_product`

sellercloud_get_product(sku: str, company_id: int | None = None)

カタログレコードを返します。SKUが会社のカタログに存在しない場合は data: null を返します。

`sellercloud_search_orders`

sellercloud_search_orders(
    date_from: str,                      # ISO date "YYYY-MM-DD"
    date_to: str,                        # ISO date "YYYY-MM-DD"
    company_id: int | None = None,
    query: str | None = None,
    limit: int = 200,                    # max 1000
)

ページネーションは透過的に処理されます。SellerCloudのページサイズ上限は50ですが、ツールは limit までページを収集します。limit を超える注文があった場合、レスポンスには limit_reached: true が含まれます。

`sellercloud_get_order`

sellercloud_get_order(order_id: int)

完全な注文レコード（Items[]を含む）を返します。404の場合は data: null を返します。

`sellercloud_get_inventory`

sellercloud_get_inventory(sku: str, company_id: int | None = None)

返されるレコードには以下が含まれます：

InventoryAvailableQty — APIが現在販売可能とみなす数量
PhysicalQty — 手持ち数量
ReservedQty — 未処理の注文のために確保されている数量
OnOrder — 入荷予定数量

「販売可能な数量」としては InventoryAvailableQty を使用してください。

`sellercloud_list_channels`

sellercloud_list_channels(company_id: int | None = None)

会社に設定されているチャネルフィードのリストを返します。各レコードには ChannelID、Name、Active が含まれます。

`sellercloud_get_channel_listing`

sellercloud_get_channel_listing(channel_id: int, sku: str)

チャネルごとのリスティング詳細。マーケットプレイス間の価格をスポットチェックするのに便利です。

ローカル開発

git clone https://github.com/alveyautomation/sellercloud-mcp
cd sellercloud-mcp
python -m venv .venv && source .venv/bin/activate    # Windows: .venv\Scripts\activate
pip install -e ".[dev]"
pytest                                                # 44 tests, ~4s

プリコミットフック（gitleaks、ruff、フォーマッタ、テナントフィンガープリントスクラバー）：

pip install pre-commit
pre-commit install

実際のSellerCloudサンドボックスアカウントに対する統合テストは SELLERCLOUD_INTEGRATION_TESTS=1 で制御されます。通常のコントリビューションには必須ではありません。

トラブルシューティング

Failed to obtain SellerCloud token — ユーザー名/パスワードが拒否されました。最も一般的な原因：アカウントで2FAが有効になっているか、ロックアウトされています。SellerCloudの POST /api/token エンドポイントは2FAなしのサービスアカウントを想定しています。

Missing required environment variables — .env が読み込まれる前にサーバーが起動しようとしました。親シェルで変数をエクスポートするか、MCPホストの設定の env ブロックにそれらが含まれていることを確認してください。

データがあるはずなのに結果が空 — company_id が正しいか確認してください。SellerCloudは、companyID を明示的に渡さない限り、認証されたユーザーのデフォルト会社のみを返します。

ページネーションが遅い — ページサイズは弊社ではなくSellerCloudによって50に制限されています。大きな日付範囲を指定する場合、複数回の往復が発生することを想定してください。

コントリビューション

Issueやプルリクエストを歓迎します。以下の点にご注意ください：

PRを開く前に pytest を実行してください (pip install -e ".[dev]")。
pre-commit run --all-files を実行してください。
v0.1の範囲内では読み取り専用の追加に留めてください。書き込みエンドポイントはv0.2で追加されます。
テストには合成データのみを使用してください。実際のSKU、顧客名、注文番号は使用しないでください。

ライセンス

MIT — LICENSE を参照してください。

免責事項

sellercloud-mcp は非公式のサードパーティ統合です。SellerCloud, Inc.によって承認、提携、サポートされているものではありません。 「SellerCloud」はSellerCloud, Inc.の商標です。自己責任で使用し、本番環境での意思決定に使用する前に、テナントに対して動作を確認してください。

Available Tools

7 tools

sellercloud_get_channel_listingA

Fetch the per-channel listing record for a single SKU.

Args: channel_id: SellerCloud ChannelID (integer). sku: Exact SKU.

Returns: JSON envelope. data is the listing record, or null if the SKU is not listed on the given channel.

ParametersJSON Schema

Name	Required	Description	Default
`channel_id`	Yes
`sku`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.1/5.0

Behavior4/5

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

Despite no annotations, the description discloses the return format (JSON envelope with data field) and the null case when SKU is not listed. This provides adequate transparency for a read-only operation.

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, using three sentences to convey purpose, parameters, and return value. Every sentence is meaningful and front-loaded.

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?

Given an output schema exists, the description sufficiently covers the tool's functionality, input requirements, and output behavior (including null). It is complete for the task of selecting and invoking the tool.

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 description coverage is 0%, so the description carries the burden. It reiterates the types (integer, exact SKU) which matches the schema, but does not add additional meaning or constraints beyond what is obvious from names and types.

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 clearly states it fetches the per-channel listing record for a single SKU, using a specific verb and resource. It distinguishes itself from sibling tools like sellercloud_get_inventory or sellercloud_get_product by focusing on channel listings.

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

Usage Guidelines3/5

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

The description implies usage for retrieving a listing by channel and SKU, but does not explicitly state when not to use it or mention alternative tools. No guidance on prerequisites or context is provided.

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

sellercloud_get_inventoryA

Fetch the current inventory record for a single SKU.

Args: sku: Exact SKU / InventoryID. company_id: CompanyID scoping the lookup.

Returns: JSON envelope. data is the inventory record (with on-hand, reserved, on-order, available qty fields), or null if absent.

ParametersJSON Schema

Name	Required	Description	Default
`sku`	Yes
`company_id`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description must cover behavioral traits. It states 'Fetch,' implying a read-only operation, and describes the return format including null for absent records. It does not mention authorization or side effects, but the context suggests a safe read.

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 highly concise with no wasted words. It front-loads the core action in the first sentence, then efficiently lists parameters and return values in a structured format.

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?

For a simple tool with two parameters and an output schema (though not explicitly shown), the description fully explains the purpose, parameters, and return value. It covers edge cases (null if absent) and key fields in the response.

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?

Schema coverage is 0% meaning no descriptions in the schema. The description adds meaning: 'sku' is described as 'Exact SKU / InventoryID' and 'company_id' as 'CompanyID scoping the lookup,' which clarifies their roles beyond the type-only 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 clearly states it fetches inventory for a single SKU, using a specific verb ('Fetch') and resource ('inventory record'). This distinguishes it from sibling tools like sellercloud_get_order or sellercloud_get_product, which target different entities.

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 specifies it's for a single SKU and lists required parameters. However, it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. The purpose is clear enough for an agent to infer usage.

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

sellercloud_get_orderA

Fetch full order detail including line items.

Args: order_id: SellerCloud OrderID (integer).

Returns: JSON envelope. data is the order record, or null if the order does not exist.

ParametersJSON Schema

Name	Required	Description	Default
`order_id`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so description bears full burden. It discloses that it returns null if order not found, but does not mention authentication requirements, rate limits, or any side effects. Minimal behavioral info.

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?

Extremely concise: four lines total. Front-loaded with purpose, then structured parameter and return descriptions. No redundant sentences.

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?

For a simple tool with 1 parameter and an output schema, the description covers the core functionality, parameter meaning, and return behavior. Missing usage guidance and behavioral details (rate limits, auth) but acceptable given low complexity.

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 0% (no param descriptions in schema). Description adds 'SellerCloud OrderID (integer)', which gives context beyond the schema's 'Order Id' title and integer type. However, it does not elaborate on format or possible values.

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?

Clearly states 'Fetch full order detail including line items.' Identifies specific verb and resource. Distinguishes from siblings like sellercloud_search_orders (search vs fetch) and sellercloud_get_product (different resource).

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

Usage Guidelines3/5

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

Does not explicitly state when to use this tool vs alternatives. Usage is implied by requiring an order_id, but no guidance on context (e.g., use when you have an ID, vs search_orders when you don't).

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

sellercloud_get_productA

Fetch the full catalog record for a single SKU.

Args: sku: Exact SKU / ProductID to look up. company_id: CompanyID scoping the lookup.

Returns: JSON envelope. data is the product record, or null when the SKU is not present in the company's catalog.

ParametersJSON Schema

Name	Required	Description	Default
`sku`	Yes
`company_id`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the return format as a JSON envelope and the possibility of null for missing SKU, but lacks details on idempotency, side effects, or rate limits.

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 concise with a structured Args and Returns section, front-loaded with the main purpose, and no unnecessary 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's low complexity and the presence of an output schema, the description adequately covers purpose, parameters, and return shape. However, it could mention the absence of pagination or limits on the record size.

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 0% description coverage, so the description compensates by clarifying 'sku' as 'Exact SKU / ProductID' and 'company_id' as 'CompanyID scoping the lookup', adding meaning beyond the raw types.

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 the verb 'Fetch' and specifies the resource as 'full catalog record for a single SKU', clearly distinguishing it from sibling tools like 'sellercloud_search_products' which implies search functionality.

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 states 'for a single SKU', implying use when exact SKU is known. However, it does not explicitly mention when not to use or compare with alternatives like 'sellercloud_get_channel_listing'.

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

sellercloud_list_channelsA

List configured channel feeds for the given company.

Args: company_id: CompanyID scoping the lookup.

Returns: JSON envelope. data.channels is the list of channel records.

ParametersJSON Schema

Name	Required	Description	Default
`company_id`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A3.8/5.0

Behavior3/5

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

Describes return structure as 'JSON envelope with data.channels'. Given no annotations, it adds some context (scoping lookup by company_id) but lacks details on side effects, rate limits, or behavior with null company_id.

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?

Two sentences in a clean Args/Returns format. No superfluous information.

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?

For a simple list operation, the description covers purpose, parameter role, and return structure. Lacks only minor details like read-only hint or error cases.

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?

Only parameter 'company_id' is explained as 'CompanyID scoping the lookup'. Adds meaningful context beyond the schema title, compensating for 0% schema description coverage.

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?

Clearly states 'List configured channel feeds for the given company'. Verb (List) and resource (channel feeds) are specific. Differentiates from sibling 'sellercloud_get_channel_listing' by being a list operation.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. No mention of when not to use or when to prefer a sibling like 'sellercloud_get_channel_listing'.

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

sellercloud_search_ordersA

Search orders created in the inclusive [date_from, date_to] window.

Args: date_from: ISO date (YYYY-MM-DD), start of window. date_to: ISO date (YYYY-MM-DD), end of window. company_id: CompanyID to scope the search to. If omitted, returns orders for the authenticated user's default company. query: Optional free-text filter applied server-side. limit: Cap on yielded orders (default 200, max 1000). The underlying API caps page size at 50; pagination is handled transparently.

Returns: JSON envelope. data.orders is the list of order records.

ParametersJSON Schema

Name	Required	Description	Default
`date_from`	Yes
`date_to`	Yes
`company_id`	No
`query`	No
`limit`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description adequately discloses behavioral traits: pagination is handled transparently, limit caps (default 200, max 1000), default company behavior for company_id. This goes beyond basic parameter names.

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 description is well-structured with a brief purpose, clear args list, and returns section. It is slightly verbose but every sentence adds value. No superfluous content.

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 5 parameters and an output schema, the description covers date range, optional filters, pagination, limit, and return envelope. It could mention error handling or rate limits, but overall it is sufficiently complete for effective tool use.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must fully explain parameters. It does: date_from/date_to with ISO format, company_id with default behavior, query as free-text filter, limit with default and max. This adds significant meaning beyond the schema titles.

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 clearly states 'Search orders created in the inclusive [date_from, date_to] window.' This specifies the verb (search), resource (orders), and scope (date range), distinguishing it from sibling tools like sellercloud_get_order (single order) and sellercloud_search_products (product search).

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

Usage Guidelines3/5

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

The description implies usage for browsing orders within a date window but does not explicitly state when to use this tool over alternatives like sellercloud_get_order or sellercloud_search_products. No when-not guidance or exclusions are provided.

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

sellercloud_search_productsA

Search the SellerCloud catalog by name, SKU, or attribute.

Args: query: Free-text search string. Matches against product name, SKU, and indexed attributes. company_id: SellerCloud CompanyID to scope the search to. Falls back to SELLERCLOUD_DEFAULT_COMPANY_ID if omitted. page: 1-indexed page number. page_size: Page size (max 50 enforced server-side).

Returns: JSON envelope: {"ok": true, "data": {"items": [...], "total": N}}.

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes
`company_id`	No
`page`	No
`page_size`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It reveals behavioral details like page_size max 50 enforced server-side, pagination behavior, and the response envelope. It does not mention authentication, rate limits, or case sensitivity, but for a search tool the provided info is adequate.

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 description is well-structured using bullet points for parameters and a clear Returns section. It is concise but could be slightly more compact (e.g., removing the docstring formatting overhead). Still, every sentence adds value.

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 4 parameters, no annotations, and an output schema (though not provided), the description covers parameter semantics, pagination, and return format. It lacks cross-referencing to siblings or mention of authorization, but overall it is complete for a search operation.

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

Parameters5/5

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

The schema has 0% description coverage, so the description must compensate. It does so excellently by explaining that query is free-text, company_id has a fallback default, page is 1-indexed, and page_size is capped at 50. This adds substantial meaning beyond the schema's type-only definitions.

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 clearly states 'Search the SellerCloud catalog by name, SKU, or attribute,' providing a specific verb and resource. It distinguishes itself from sibling tools like sellercloud_get_product (single product retrieval) and sellercloud_search_orders (different entity), making the tool's role unambiguous.

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 for general product searching but does not explicitly state when to avoid it or compare it to siblings like sellercloud_get_channel_listing or sellercloud_get_inventory. However, the parameter descriptions give clear context on how to use the tool effectively.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

7 tool updatesv0.1.0Apr 27, 2026
- First observedsellercloud_get_channel_listing
- First observedsellercloud_get_inventory
- First observedsellercloud_get_order
- First observedsellercloud_get_product
- First observedsellercloud_list_channels
- First observedsellercloud_search_orders
- First observedsellercloud_search_products

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored 2026-04-27 05:10 across 7 tools

Disambiguation5/5

Each tool targets a distinct resource or action: product, inventory, order, channel listing, channels list, and two searches. No overlap in purpose.

Naming Consistency5/5

All tools follow a consistent `sellercloud_verb_noun` pattern (get_, list_, search_), with clear verb choice for the operation type.

Tool Count5/5

7 tools is well-scoped for a seller cloud integration covering core data retrieval: product, inventory, order, and channel information.

Completeness3/5

The tool set is read-only, covering get and search for products, orders, inventory, and channels. Missing update/create operations that agents might need for full workflow support.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

Agent Central A
to.agentcentral
Hosted Amazon Seller Central and Amazon Ads MCP server for Claude, ChatGPT, Cursor, and agents.
Customer Support E-commerce & Retail
9726
DataDoe MCPOAuth
com.datadoe
Hosted Amazon Seller and Vendor MCP server for Claude, ChatGPT, Cursor, Codex, Gemini, Copilot.
E-commerce & Retail CRM
215
Terra Natural Seller MCPOAuth
uk.co.sellermcp
Connect Amazon Seller Central to Claude or ChatGPT via MCP. Orders, inventory, pricing, fees, FBA.
E-commerce & Retail Finance
1
Amazon Seller Central & Ads MCP A
ai.agentxray
Amazon Seller Central and Ads inside Claude or ChatGPT. Real fees from your own settlements.
E-commerce & Retail Finance
281

Related MCP Servers

TripleWhale MCP Serverofficial
E-commerce & Retail Search Databases
Triple-Whale
A
license
Not graded
quality
C
maintenance
An implementation of Model Context Protocol (MCP) that allows users to interact with TripleWhale's e-commerce analytics platform using natural language queries through Claude Desktop.
Updated a year ago (2025-09-30 12:49 UTC)
106 npm
7
MIT
keycrm-mcp
CRM E-commerce & Retail
IvanKlymenko
F
license
Not graded
quality
C
maintenance
A Model Context Protocol server that lets Claude manage keyCRM catalogue, stock, orders, customers, pipelines, and more via natural language.
Updated 7 months ago (2026-03-25 11:17 UTC)
3
-
Amazon Seller MCP Server -
E-commerce & Retail Finance Marketing
Deltologic
A
license
Not graded
quality
B
maintenance
Hosted Amazon Seller Central & Vendor Central MCP server. Connect Claude, ChatGPT, Cursor, Codex, Gemini, and GitHub Copilot to live Amazon SP-API and Amazon Ads API data.
Updated 8 days ago (2026-10-06 10:39 UTC)
15
MIT
MCP4Acumatica
ERP Systems Finance CRM
NologyAcu
A
license
Not graded
quality
C
maintenance
A Model Context Protocol server that connects Claude to Acumatica ERP, enabling AI-driven data access with per-user OAuth, role-based permissions, and automatic sensitive field redaction.
Updated 2 months ago (2026-08-21 13:15 UTC)
Apache 2.0

sellercloud-mcp

このプロジェクトの目的

できること

ツール (v0.1, すべて読み取り専用)

インストール

認証情報の構成

Claude Codeへの接続

Claude Desktopへの接続

ツールリファレンス

sellercloud_search_products

sellercloud_get_product

sellercloud_search_orders

sellercloud_get_order

sellercloud_get_inventory

sellercloud_list_channels

sellercloud_get_channel_listing

ローカル開発

トラブルシューティング

コントリビューション

ライセンス

免責事項

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

TripleWhale MCP Serverofficial

`sellercloud_search_products`

`sellercloud_get_product`

`sellercloud_search_orders`

`sellercloud_get_order`

`sellercloud_get_inventory`

`sellercloud_list_channels`

`sellercloud_get_channel_listing`