mcp-server

get_marketplace

Read-onlyIdempotent

Get the full detail of one marketplace: identity, state and wizard steps. Use this to read its configuration. CRITICAL — read activationBehavior in the RESULT: 'summary_step_activates_and_submits_all' means activate_marketplace ACTIVATES the marketplace and publishes EVERY matching product to the LIVE channel, so to test safely set MANUAL mode FIRST (set_marketplace_manual_mode) — it then reads 'summary_step_activates_no_auto_submit' and activation auto-submits nothing; 'already_active' = already live. Returns {integrationId, projectId, name, channelCode, kind, definitionCode, status, ready, lastStep, isReady, isConnected, isOverlimit, primarySync, orderSync, canEnableOrderSync, productMode, orderMode, taxonomyCode, categoryMappingRequired, connectionStatus, connectionMessage, connectionExpiresAt, steps:[{type, label, sort, index, ready, current, fields:[{code, label, type, required, options, optionsSource, optionsPending, htmlAttributes, value, help, showIf, hiddenIf}]}], editUrl, activationBehavior}. steps describe the setup wizard: 'current' is the next step to configure (via configure_marketplace_step, targeting it by its index — two steps can share a type) and 'ready' marks completed steps; fields is that step's input schema. Do not cache this schema across the auth step: field metadata from the channel connection (options, resolved defaults) does not exist before it. The connection/auth step (OAuth or credentials) is NOT configurable via MCP — the user completes it in the browser / Koongo UI. taxonomyCode is set automatically from the channel and is read-only. Full field-by-field reference (step payloads, optionsPending, connection health, category mapping, order sync, marketplace_status): call get_koongo_help with slug 'marketplace-wizard-steps'. marketplace_id is the id from list_marketplaces / create_marketplace. project_id is OPTIONAL (inferred for a single-project customer; project_id_required otherwise — then call list_projects).

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": {
      "marketplace_id": "<marketplace_id>"
    },
    "name": "get_marketplace"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	No
`marketplace_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds real behavioral context: activationBehavior enum meanings, that field metadata (options, resolved defaults) does not exist before the auth step so the schema must not be cached, and that taxonomyCode is read-only. That is exactly the beyond-annotations disclosure this dimension rewards.

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 CRITICAL warning are front-loaded, and most sentences carry load. The long comma-separated return-field enumeration is dense and partly duplicated by the later pointer to get_koongo_help slug 'marketplace-wizard-steps', which slightly hurts scannability.

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 return shape, explains steps/fields semantics and index targeting, and covers the activation and connection caveats. An agent could call this and interpret the result correctly without any other source.

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 0%, so the description must carry parameter meaning — and it does: marketplace_id comes from list_marketplaces/create_marketplace, and project_id is optional (inferred for single-project customers) with the project_id_required fallback pointing to list_projects. Both params are fully disambiguated despite an empty schema.

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

Purpose4/5

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

Opens with a specific verb and resource: 'Get the full detail of one marketplace: identity, state and wizard steps,' and scopes it to 'one'. It implicitly distinguishes itself from list_marketplaces ('one', and the id comes from that list) and from marketplace_status (full detail vs. status), though it never names a sibling as an explicit alternative.

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?

Gives explicit usage context ('Use this to read its configuration') plus hard ordering guidance: read activationBehavior, and to test safely call set_marketplace_manual_mode FIRST before activate_marketplace. It also states a genuine exclusion — the OAuth/credentials step is NOT configurable via MCP and must be finished in the browser — and routes to get_koongo_help for depth.

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?