@ktmcp/beezup

SetChannelCatalogMarketplaceSettings

Save new marketplace settings for a channel catalog to update store configuration and manage marketplace integration.

Instructions

Save new marketplace settings for a channel catalog

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": {
      "channelCatalogId": "<channelCatalogId>"
    },
    "name": "SetChannelCatalogMarketplaceSettings"
  }
}

Input Schema

Name	Required	Description	Default
`body`	No	Request body
`channelCatalogId`	Yes	Channel Catalog Id to query

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Save new marketplace settings' without explaining effects (overwrite vs. append), idempotency, required permissions, or rate limits. This is insufficient for safe agent invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it omits crucial details, making it under-specified rather than effectively concise. No structure (e.g., bullet points) is needed for such a short description, so it achieves minimal adequacy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of marketplace settings (nested body object, no output schema, no annotations), the description is incomplete. It does not mention what settings are available, the meaning of 'new', or the response format, leaving significant gaps for the agent.

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

Parameters2/5

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

The input schema covers both parameters with descriptions, but the descriptions are poor: channelCatalogId is described as 'to query' (ill-fitting for a save operation), and body is only 'Request body' with no structure. The tool description adds no extra meaning beyond these vague schema descriptions.

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?

The description states the verb 'Save' and the resource 'marketplace settings for a channel catalog', clearly indicating the action and target. It distinguishes from sibling tools like GetChannelCatalogMarketplaceSettings (read) and ConfigureChannelCatalogGeneralSettings (broader settings). However, 'new' ambiguously implies creation versus update, slightly reducing clarity.

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 guidance is provided on when to use this tool versus siblings such as ConfigureChannelCatalogCostSettings or ConfigureChannelCatalogGeneralSettings. The description lacks context about prerequisites, typical use cases, or when to avoid using it.

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

Deploy Server