Skip to main content
Glama

BetaFinds

by io.github.pendurov

create_startup

Create a new startup on BetaFinds (submitted for review). Upload the logo and screenshots first via upload_image (or POST https://betafinds.com/api/v1/images) and pass the returned URLs here. Set the category by slug — get the list via list_categories (a category name also works, case-insensitive).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoProduct website URL (required for stage=LAUNCHED, optional for prelaunch)
logoNoLogo URL from upload_image (optional)
nameYesProduct name
tagsNoTags (up to 6)
stageNoProduct stage: PRELAUNCH — preparing to launch, BETA — recruiting beta testers, LAUNCHED — already launched (default)
taglineYesOne-line tagline (up to 160 characters)
appStoreUrlNoApp Store page link (iOS)
descriptionYesFull description (min 50 characters)
screenshotsNoScreenshot URLs from upload_image (up to 5, optional)
category_slugNoCategory slug (e.g. ai, saas, fintech)
googlePlayUrlNoGoogle Play page link (Android)
testflightUrlNoTestFlight link (iOS beta)
prelaunch_readyNoWhat is already done: prototype, design, private beta… (up to 1000 characters)
prelaunch_promiseNoWhat a waitlist subscriber will get (up to 1000 characters)
prelaunch_audienceNoWho the product is for (up to 1000 characters)
target_launch_dateNoEstimated launch date in YYYY-MM-DD format (for prelaunch; empty string clears it)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
slugNo
statusNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • addedInput schema / properties / prelaunch_audience
      Added value: +{
+  "description": "Who the product is for (up to 1000 characters)",
+  "type": "string"
+}
    • addedInput schema / properties / prelaunch_promise
      Added value: +{
+  "description": "What a waitlist subscriber will get (up to 1000 characters)",
+  "type": "string"
+}
    • addedInput schema / properties / prelaunch_ready
      Added value: +{
+  "description": "What is already done: prototype, design, private beta… (up to 1000 characters)",
+  "type": "string"
+}
    • addedInput schema / properties / target_launch_date
      Added value: +{
+  "description": "Estimated launch date in YYYY-MM-DD format (for prelaunch; empty string clears it)",
+  "type": "string"
+}
  2. Changed6 schema fields changed
    • changedInput schema / properties / appStoreUrl / description
      Previous value: -"Ссылка на страницу в App Store (iOS)"New value: +"App Store page link (iOS)"
    • changedInput schema / properties / googlePlayUrl / description
      Previous value: -"Ссылка на страницу в Google Play (Android)"New value: +"Google Play page link (Android)"
    • addedInput schema / properties / stage
      Added value: +{
+  "description": "Product stage: PRELAUNCH — preparing to launch, BETA — recruiting beta testers, LAUNCHED — already launched (default)",
+  "enum": [
+    "PRELAUNCH",
+    "BETA",
+    "LAUNCHED"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / testflightUrl / description
      Previous value: -"Ссылка на TestFlight (бета для iOS)"New value: +"TestFlight link (iOS beta)"
    • changedInput schema / properties / url / description
      Previous value: -"Product website URL"New value: +"Product website URL (required for stage=LAUNCHED, optional for prelaunch)"
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "tagline",
-  "description",
-  "url"
-]New value: +[
+  "name",
+  "tagline",
+  "description"
+]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Discloses that the startup goes into review (submitted for review), and gives prerequisites for assets. Annotations indicate mutation but not destructive; description adds context about submission process.

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?

Three sentences, front-loaded with purpose and result, then usage tips. No unnecessary 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?

With output schema, high parameter coverage, and annotations, description covers review process and dependencies. Could mention defaults (e.g., stage default) but overall adequate.

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%, so baseline 3 applies. Description adds value for logo, screenshots, and category_slug but does not elaborate on other parameters beyond schema descriptions.

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?

Description clearly states 'Create a new startup on BetaFinds (submitted for review)', with specific verb and resource, and distinguishes from siblings like update_startup.

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?

Provides explicit guidance to upload logo/screenshots first via upload_image and set category via list_categories, but no explicit when-not-to-use or alternatives.

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

All BetaFinds toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool has a clear, distinct purpose: startup CRUD, stage management, release handling, image upload, category listing, updates, reviews, waitlist. No overlapping ambiguities.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_startup, list_categories, upload_image). No mixing of conventions.

Tool Count5/5

14 tools is well-scoped for a startup management platform. Each tool serves a specific function without redundancy, covering core workflows.

Completeness4/5

Covers the full lifecycle: create, update, stage transitions, launch, releases, file uploads, images, categories, updates, waitlist, and reviews. Missing delete startup or team management, but these are minor gaps.

Resources