mcp-server

list_marketplaces

Read-onlyIdempotent

List the CREATED marketplace integrations of a project — the marketplace integrations that already exist, not the catalog of channels you can add (use list_marketplace_channels for that). Use this to find an existing marketplace and its marketplace_id. Each item is {integrationId, projectId, name, channelCode, kind, definitionCode, status, ready, lastStep, isReady, isConnected, isOverlimit, productMode, orderMode, orderSync}. The response wrapper is {integrations, returned, total}. project_id is OPTIONAL: with it you get that project's marketplaces; WITHOUT it you get marketplaces across ALL your projects (each item carries its projectId). If a call returns project_id_required, pick a project (see list_projects) and pass its project_id. integrationId is what you pass as marketplace_id to get_marketplace / marketplace_status and the other marketplace tools.

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_marketplaces"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare a safe, idempotent read, so the bar is lower, yet the description still adds real behavior: the shape of each item, the {integrations, returned, total} wrapper, and the crucial scoping rule that omitting project_id fans out across ALL projects while supplying it narrows to one. It also discloses a specific error token and the recovery step, which is behavior no annotation or schema field conveys.

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?

Front-loaded with purpose and the sibling exclusion before the mechanics, which is the right ordering. The one weakness is the inline dump of twelve item fields plus the wrapper keys, which is heavy prose for information an enumerating caller mostly needs to skim, though it does serve as a de facto output schema since none is supplied.

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?

There is no output schema, so the description compensates by enumerating item fields and the response wrapper, and it covers scoping, error handling, and ID chaining into related tools. For a one-optional-parameter list tool this leaves nothing an agent needs unanswered.

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% and the single parameter has no documented semantics, so the description must carry it — and it does, explaining that project_id is optional and describing exactly what happens with and without it, plus the project_id_required fallback. Without this text the integer parameter would be opaque.

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 names a specific verb and resource ('List the CREATED marketplace integrations of a project') and immediately disambiguates from the nearest confusing sibling by contrasting with 'the catalog of channels you can add' and naming list_marketplace_channels. An agent can distinguish this from list_marketplace_channels, get_marketplace, and list_marketplace_items without opening any 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?

Explicit when-to-use is given ('Use this to find an existing marketplace and its marketplace_id'), the when-not is given via the channel-catalog exclusion, and the downstream alternative is named ('integrationId is what you pass as marketplace_id to get_marketplace / marketplace_status'). Even the failure path is routed: on project_id_required, go 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?