mcp-server

get_marketplace_channel

Read-onlyIdempotent

Get, for ONE marketplace channel, the integration TYPES it supports and each type's capabilities. Use this to choose the integration type before create_marketplace. Returns {channelCode, label, kind, devOnly, multichannel, multichannelCode, definitions:[{definitionCode, type, typeLabel, label, versionType, primary, capabilities:{orderSync, categoryMapping, productFilter, attributeMapping}}]}. kind is always 'marketplace' here. versionType is 'primary' or 'secondary' and primary marks the default definition. capabilities tell you what a given definition supports (order sync, category mapping, product filtering, attribute mapping). Call this before create_marketplace to choose the right definition for the channel. channel_code is the channelCode from list_marketplace_channels. project_id is OPTIONAL (inferred for a single-project customer; project_id_required otherwise — then call list_projects and pass its project_id).

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": {
      "channel_code": "<channel_code>"
    },
    "name": "get_marketplace_channel"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	No
`channel_code`	Yes	channelCode of the marketplace channel (from list_marketplace_channels).

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real behavioral content not covered by them: the fixed value of 'kind' for this endpoint, the meaning of versionType ('primary' is the default definition), and what capabilities flags represent. It stops short of explaining failure modes or what an unknown channel_code returns, but the value beyond annotations is substantial.

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?

Content is front-loaded and the return shape is described in a compact inline notation, but there is noticeable repetition — the 'call this before create_marketplace' instruction appears twice and the capabilities explanation is restated ('capabilities tell you what a given definition supports' after already enumerating the four flags).

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 carries the return contract and does so thoroughly — every field of the response object is enumerated and the non-obvious ones (kind, versionType, primary, capabilities) are explained. Together with the parameter guidance, an agent can call this correctly without further inference.

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 coverage is only 50% (project_id is undocumented in the schema), and the description compensates fully: it explains channel_code is the channelCode from list_marketplace_channels and clarifies project_id is OPTIONAL, inferred for single-project customers, and required only in the project_id_required case.

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 opens with a precise verb+resource+scope ('Get, for ONE marketplace channel, the integration TYPES it supports and each type's capabilities'), which is enough to distinguish it from get_marketplace, get_marketplace_attributes, and list_marketplace_channels.

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 names both the trigger ('Use this to choose the integration type before create_marketplace') and the prerequisites, including where channel_code comes from (list_marketplace_channels) and the project_id fallback path (list_projects when project_id_required).

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?