Skip to main content
Glama
Sign In
@ktmcp/beezup

@ktmcp/beezup

by ktmcp-cli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

PublishCatalogToMarketplace

Publish a BeezUP catalog to a marketplace by submitting the marketplace technical code and account ID.

Instructions

[PREVIEW] Launch a publication of the catalog to the marketplace

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": {
      "marketplaceTechnicalCode": "<marketplaceTechnicalCode>",
      "accountId": "<accountId>"
    },
    "name": "PublishCatalogToMarketplace"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoRequest body
accountIdYesAccount Id to query (required)
marketplaceTechnicalCodeYesMarketplace Technical Code to query (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Launch a publication' but does not specify whether this is synchronous or asynchronous, what side effects occur, or any required permissions. The '[PREVIEW]' tag suggests it might be preliminary, but no further details.

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?

The description is extremely concise, front-loading the action. However, it may be too brief for the complexity of the operation. Still, every word serves a purpose.

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 lack of output schema and the complexity of publishing to a marketplace, the description is incomplete. It does not mention the return value (e.g., publication ID) or the need to monitor publication status via other tools.

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

Parameters3/5

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

Schema coverage is 100% and each parameter has a description, though minimal (e.g., 'Request body' for body). The tool description adds no extra meaning beyond the schema, so baseline 3 applies.

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 clearly states the action 'Launch a publication' and the resource 'catalog to the marketplace', using a specific verb and resource. It distinguishes from sibling tools like catalog configuration or harvesting.

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 on when to use this tool, prerequisites, or alternatives. For example, it does not mention that the catalog should be configured first or that a marketplace account must be synchronized.

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

Deploy Server

Other Tools