mcp-server

list_marketplace_channels

Read-onlyIdempotent

Search the CATALOG of marketplace channels you can ADD — every sales channel (Amazon, eBay, Kaufland, Bol, Zalando, comparison sites, …) you can create a marketplace integration for (to list the marketplaces that ALREADY exist, use list_marketplaces). Use this when the user wants to add a marketplace and needs its channel. The catalog is large (many country variants), so it is SEARCHABLE + PAGED: pass query to match a channelCode/label (e.g. "amazon"), and page with limit/offset (the response carries hasMore + nextOffset). Response = {channels, returned, total, kind, hasMore, nextOffset}; each channel = {channelCode, label, kind, available, availabilityReason, authType, orderSyncSupported, multichannel, multichannelCode, primaryChannelCode, devOnly, feedManagerUrl}. available=false means you cannot add it now and availabilityReason says why: 'not_included' or another reason (not available for this Koongo account), or 'fallback' (feedManagerUrl — connect it via Feed Manager). authType is oauth|credentials|null. Use channelCode with get_marketplace_channel (to see the definition types + capabilities) and then create_marketplace. project_id is OPTIONAL (inferred for a single-project customer; project_id_required otherwise — then call list_projects).

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": "list_marketplace_channels"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max channels per page (default 50, max 200).
`query`	No	Filter to channels whose code or label contains this text.
`offset`	No	Channels to skip; use the response nextOffset to page.
`project_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real context: the catalog is large with country variants, it is searchable and paged, and available=false plus availabilityReason ('not_included', 'fallback' via Feed Manager) explains why a channel cannot be added. It does not discuss rate limits or result ordering, which keeps it from a 5.

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?

Purpose and the list_marketplaces disambiguation are front-loaded, and the search/paging constraint follows before the response detail. The exhaustive enumeration of thirteen response fields is dense but justified since there is no output schema; still, it could have been trimmed to the decision-relevant fields.

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 no output schema, the description supplies the full response shape and field semantics (available/availabilityReason/authType), the paging mechanism, and the follow-up tool chain. Nothing an agent needs to call this correctly and interpret the result is missing.

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 75%, and the description adds meaning where the schema is silent — notably that project_id is OPTIONAL and inferred for single-project customers, and that limit/offset drive a hasMore/nextOffset paging loop. The query explanation largely restates the schema's 'code or label contains this text'.

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?

States a specific verb and resource — searching the CATALOG of marketplace channels you can ADD — and immediately contrasts it with list_marketplaces, which lists ones that already exist. An agent can distinguish it from the sibling without opening either schema.

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?

Explicitly says when to use it ('when the user wants to add a marketplace and needs its channel') and names the alternative (list_marketplaces) for the other case. It also prescribes the downstream sequence — use channelCode with get_marketplace_channel, then create_marketplace — and covers the project_id fallback to list_projects.

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

All mcp-server tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?