Loading ToolBench
Model Context Protocol (MCP) server for BetaDrop. Lets AI assistants publish iOS/Android builds, manage tokens, and list build history — directly from your IDE.
betadrop-mcp demonstrates solid tool design with consistent naming (verb_noun pattern), comprehensive parameter schemas, and clear descriptions. All 11 tools have explicit definitions with input schemas and descriptions. However, output schemas are not documented, error handling lacks recovery guidance, and some parameter descriptions could be more prescriptive about constraints and formats. Tool names are action-oriented (login, publish, list) and parameter types are properly declared. The server follows good composition patterns with single-responsibility tools and proper chaining (e.g., publish → upload_status). Main gaps: no documented return types, missing enum constraints on some parameters, and generic error messages.
Get a quick reference of all available BetaDrop MCP tools, their inputs, and example prompts.
List recent builds published to BetaDrop, optionally filtered by platform and status.
List all expired builds on BetaDrop. Shortcut for listing builds with status 'expired'. Shows expiry reason and details.
Configure API authentication with a BetaDrop token. Validates the token against the server and saves credentials to the shared CLI config.
Revoke the active token on the server and clear local credentials.
Publish an iOS (.ipa) or Android (.apk) build to BetaDrop.
Output schemas not documented. No tool returns a documented response structure. LLMs cannot plan downstream calls or extract required fields (e.g., what does betadrop_publish return? Is it an install link, a build ID, or a full build object?). This forces agents to guess and wastes tokens on clarification.
Error handling lacks recovery guidance. No tool provides actionable error messages or suggests next steps. E.g., if betadrop_login fails with 'Invalid token', the LLM has no guidance on whether to retry, ask the user for a new token, or check the API URL. Generic errors block agent recovery.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
Create a new CLI token. The plaintext token is shown exactly once — copy it immediately.
Revoke a CLI token by its ID.
List all active CLI tokens for the current account.
Get the result of the most recent betadrop_publish upload, including the install link. Call this only when betadrop_publish reported the upload was still running.
Check authentication status and show the active account and BetaDrop server details.
Parameter constraints not fully specified. expiryTimeDays, expiryDownloadLimit, expiryDeviceLimit lack min/max bounds. perPage in list tools says 'max 100' but no minimum stated. LLMs may pass invalid values (e.g., perPage=0 or expiryTimeDays=-5) without validation guidance.
betadrop_help tool is meta-documentation. Its purpose ('Get a quick reference of all available tools') is vague and duplicates the ListTools capability. This tool adds little value and consumes a slot. Consider removing or clarifying when an LLM should call it vs. relying on ListTools.
Conditional parameter dependencies not documented. In betadrop_publish, expiryTimeDays only applies if expiryType is 'time' or 'combined'. This dependency is mentioned in the description but not enforced or clearly stated as a mutual constraint. LLMs may pass expiryTimeDays with expiryType='none', causing silent failures.