Skip to main content
Glama
Sign In
bolthub

bolthub

Official
by signaltech-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

publish_listing

Idempotent

Publish draft endpoints to the bolthub marketplace. Perform a dry run to preview changes, then confirm to go live and start the workspace's 30-day free trial.

Instructions

Take a workspace's draft endpoints live in the bolthub directory. Without confirm:true it is a DRY RUN that shows exactly what would go live (endpoints, prices, workspace activation) — show that to the user and get their go-ahead before re-calling with confirm:true. Publishing the first endpoint starts the workspace's 30-day free trial. Requires BOLTHUB_ACCOUNT_TOKEN.

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": "publish_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoOmitted/false = dry run (no changes). true = publish exactly what the dry run showed.
tenant_idNoWorkspace id. Omit when the account has exactly one workspace.
endpoint_idsNoSpecific endpoint ids to publish. Omit to publish every unlisted endpoint in the workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Discloses dry run behavior, token requirement, and free trial implication. Adds context beyond annotations (openWorldHint, idempotentHint, destructiveHint=false). No contradictions.

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

Conciseness5/5

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

Two concise sentences plus brief extra context. Front-loaded with main action, then detailed workflow. No wasted words.

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

Completeness4/5

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

Covers workflow, dry run, free trial, token requirement. No output schema, but behavior is well-explained. Little missing: could mention idempotency or error cases, but sufficient.

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

Parameters4/5

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

Schema coverage 100%. Description adds usage semantics: confirm as dry run vs publish, tenant_id optional for single workspace, endpoint_ids optional for all. Enriches schema details.

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?

Clearly states the action: 'Take a workspace's draft endpoints live in the bolthub directory.' Distinguishes from siblings like analyze_listing and call_api.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains dry run vs confirm workflow, that first publish starts free trial, and requires token. Lacks explicit when-not-to-use, but context is clear.

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