BetaFinds

publish_update

Publish an update (an entry in the «What's new» feed) for your startup. Subscribers receive an email summary within ~10 minutes. body supports Markdown.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "startup_slug": "<startup_slug>",
      "title": "<title>",
      "body": "<body>"
    },
    "name": "publish_update"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	Text in Markdown (10–20000 characters)
`type`	No	Type: RELEASE — new version, UPDATE — improvement, FIX — fix, NEWS — news. Defaults to NEWS.
`title`	Yes	Update title (3–200 characters)
`version`	No	Version, if applicable (e.g. 1.4.0)
`startup_slug`	Yes	Startup slug (from list_my_startups)

Output Schema

Name	Required	Description	Default
`id`	No
`message`	No
`publishedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "publishedAt": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations are provided, and the description adds value by noting that 'body supports Markdown' and that 'subscribers receive an email summary within ~10 minutes'. These details go beyond the structured annotations and help the agent understand expected behavior.

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?

The description is two sentences, no wasted words, and front-loads the purpose. Every sentence contributes meaningful information.

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?

Given the output schema exists (as per context signals), the description covers return values implicitly. It includes key details like Markdown support, email timing, and character limits from the schema. It is complete for this type of tool.

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 the baseline is 3. The description mentions Markdown support for body, which is already in the schema description ('Text in Markdown'). No additional semantic value is provided beyond the schema.

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 explicitly states the action 'publish', the resource 'update (an entry in the «What's new» feed)', and the scope 'for your startup'. This clearly distinguishes it from sibling tools like 'create_release' or 'announce_launch'.

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?

The description implies usage context by mentioning the email summary for subscribers, but it does not explicitly state when to use this tool vs alternatives (e.g., for general startup updates vs. releases or launches). However, the context is clear enough for an AI agent to differentiate.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.