BetaFinds

update_startup

Idempotent

Update an existing startup: app-store links, website, short/full description, tags, category, logo and screenshots. Upload the logo and screenshots first via upload_image and pass the returned URLs (screenshots fully replace the current set; to clear the logo, pass an empty string). Pass only the fields you want to change. See current values via list_my_startups. Note: editing an approved startup sends it back to moderation.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Product website URL
`logo`	No	Logo URL from upload_image (empty string to clear)
`tags`	No	Tags (up to 6)
`tagline`	No	One-line tagline (up to 160 characters)
`appStoreUrl`	No	App Store page link (iOS)
`description`	No	Full description (min 50 characters)
`screenshots`	No	Screenshot URLs from upload_image (up to 5; fully replace the current set)
`startup_slug`	Yes	Startup slug (from list_my_startups)
`category_slug`	No	Category slug (see list_categories)
`googlePlayUrl`	No	Google Play page link (Android)
`testflightUrl`	No	TestFlight link (iOS beta)
`prelaunch_ready`	No	What is already done: prototype, design, private beta… (up to 1000 characters)
`prelaunch_promise`	No	What a waitlist subscriber will get (up to 1000 characters)
`prelaunch_audience`	No	Who the product is for (up to 1000 characters)
`target_launch_date`	No	Estimated launch date in YYYY-MM-DD format (for prelaunch; empty string clears it)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No
`slug`	No
`status`	No
`message`	No

Schema Changelog

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

Changed4 schema fields changedJul 13, 2026

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"
+}

Changed3 schema fields changedJul 13, 2026

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)"

changedInput schema / properties / testflightUrl / description

Previous value: -"Ссылка на TestFlight (бета для iOS)"New value: +"TestFlight link (iOS beta)"

Changed2 schema fields changedJul 9, 2026

addedInput schema / properties / logo

Added value: +{
+  "description": "Logo URL from upload_image (empty string to clear)",
+  "type": "string"
+}

addedInput schema / properties / screenshots

Added value: +{
+  "description": "Screenshot URLs from upload_image (up to 5; fully replace the current set)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed2 schema fields changedJul 8, 2026

changedInput schema / properties / category_slug / description

Previous value: -"Slug категории (см. list_categories)"New value: +"Category slug (see list_categories)"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Discloses critical behaviors beyond annotations: screenshots fully replace the set, empty clears logo, editing approved startup sends to moderation. Annotations only hint idempotent and non-destructive.

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 front-loading purpose, then bullet-like listing, followed by critical notes. No fluff, every sentence earns its place.

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?

Complete coverage for a complex tool with 15 parameters: explains prerequisites, side effects, and references related tools. Output schema exists so return values need not be detailed.

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 is 100%, but description adds value by explaining relationships (logo/screenshots come from upload_image), replacement semantics, and optionality 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?

The description clearly states 'Update an existing startup' and enumerates the specific fields that can be modified, distinguishing it from sibling tools like create_startup and list_my_startups.

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: pass only changed fields, upload media first via upload_image, see current values via list_my_startups, and notes moderation effect. Lacks explicit when-not-to-use but is clear overall.

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

All BetaFinds tools Inspect

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.