Skip to main content
Glama
erova

VibeSharing MCP Server

by erova

register_prototype

Register a prototype on VibeSharing to share and gather team feedback. Confirm target collection/project with resolve_target first, then create standalone or add as a project version.

Instructions

Register a prototype on VibeSharing. Creates a standalone prototype by default. To add it as a version under an existing project, provide parent_project_id. IMPORTANT: Before calling this, use resolve_target to confirm the collection and project name with the user. Do not auto-generate names without user confirmation. Returns the VibeSharing URL where the team can view and leave feedback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the prototype (e.g., 'Dashboard Redesign v2')
descriptionNoBrief description of what this prototype demonstrates
source_codeNoOptional: Source code to upload to VibeSharing. Colleagues can download this from the prototype page.
external_urlNoURL where the prototype is deployed (e.g., https://my-app.vercel.app)
collection_idNoOptional: ID of collection (folder) to place this prototype in. Use list_collections to find the right ID.
source_filenameNoOptional: Filename for uploaded source (default: 'page.tsx')
parent_project_idNoOptional: ID of parent project if this is a version/iteration
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses default behavior (standalone), the versioning option, the user-confirmation requirement, and the return URL. While it doesn't mention every possible side effect, it covers the key behavioral constraints and output clearly.

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 concise sentences, front-loaded with the main action, then conditional behavior, an important note, and the return value. Every sentence earns its place with zero fluff.

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?

For a complex 7-param tool with no annotations or output schema, the description provides essential context: default behavior, versioning option, user-confirmation requirement, procedural prerequisite, and return URL. Since the schema fully documents parameters, the description completes the picture effectively.

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%, so the baseline is 3. The description adds contextual meaning by explaining the two creation modes (standalone vs. parent_project_id) and the resolve_target prerequisite for collection/project, enhancing understanding of parent_project_id and collection_id 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 clearly states 'Register a prototype on VibeSharing' with a specific verb and resource, and distinguishes between standalone creation and versioning under an existing project via parent_project_id. This differentiates it from siblings like deploy_prototype and upload_source.

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?

It explicitly instructs to use resolve_target before calling to confirm collection and project name, and warns against auto-generating names without user confirmation. This provides clear when-to-use guidance and an explicit prerequisite alternative.

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/erova/vibesharing-mcp'

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