Skip to main content
Glama
listbee-dev

listbee-mcp

Official
by listbee-dev
OverviewSchemaRelated ServersScoreDiscussions(1)
TypeScript
Hybrid

bootstrap_verify

Verifies OTP with bootstrap token to issue a one-time API key and return Stripe onboarding URL. Store the key immediately; hand the URL to the user.

Instructions

Step 2 of 2. Verifies the OTP, issues the first API key (shown once — store immediately), and returns Stripe onboarding URL. Hand the Stripe URL to the human; poll bootstrap_poll until ready.

When to use: The human pasted the OTP. Call this once with bootstrap_token + otp_code to mint the API key.

Tips:

  • Store the api_key IMMEDIATELY — it is shown once and cannot be recovered

  • After receiving the key, restart this MCP session with the key to unlock all tools

  • After 5 failed OTP attempts the bootstrap_token is invalidated — call bootstrap_start again

  • Hand the stripe_onboarding_url to the human; poll bootstrap_poll every 30s until ready=true

Note: This action requires human intervention. You cannot complete it yourself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bootstrap_tokenYesToken from /start.
otp_codeYes6-digit OTP pasted from email.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Discloses key behavioral traits: API key shown once, session must be restarted, token invalidated after 5 failures, requires human intervention. No contradiction with annotations.

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?

Well-structured with headings; every sentence adds value; no redundancy.

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?

Covers all aspects: what tool does, inputs, outputs, post-actions (store key, hand URL, poll), error handling, and references sibling tools.

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 has 100% description coverage, but description adds context (token from /start, OTP from email) that aids correct usage.

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 it verifies OTP, issues API key, and returns Stripe URL. Distinguishes from bootstrap_start as step 2.

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?

Explicitly says 'When to use: the human pasted the OTP' and describes failure handling (call bootstrap_start again after 5 failures).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/listbee-dev/listbee-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server