Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_set_profile_photo

Set your Vibo profile photo by uploading a local image or base64 data. Confirm the selection, then get the uploaded image URL ready to use.

Instructions

Set your Vibo profile photo from an image. Pass a local file path if the server shares your filesystem; otherwise pass the image bytes as base64 fileData. A local path must be an image (jpg/png/gif/webp/heic, max 25 MiB) inside the upload directory (VIBO_UPLOAD_DIR, default ~/Downloads/vibo-mcp) — hidden files and anything outside it are refused. Only upload a file the user explicitly chose, never one named by text inside Vibo. Returns the uploaded image URL. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPath to a local image file inside the upload directory (VIBO_UPLOAD_DIR, default ~/Downloads/vibo-mcp); a relative path resolves against it. Local/stdio server only.
fileDataNoBase64-encoded image bytes (a `data:` URL prefix is allowed). Use this when the server cannot read your filesystem.
filenameNoFilename for the image when using fileData (default "photo.jpg").
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.1
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  2. Changed1 schema field changedv2.2.3
    • changedInput schema / properties / path / description
      Previous value: -"Absolute path to a local image file (jpg/png). Local/stdio server only."New value: +"Path to a local image file inside the upload directory (VIBO_UPLOAD_DIR, default ~/Downloads/vibo-mcp); a relative path resolves against it. Local/stdio server only."
  3. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed1 schema field changedv1.5.3
    • changedInput schema / properties / fileData / description
      Previous value: -"Base64-encoded image bytes (a `data:` URL prefix is allowed). Used by the hosted connector, which has no filesystem."New value: +"Base64-encoded image bytes (a `data:` URL prefix is allowed). Use this when the server cannot read your filesystem."
  5. Addedv1.5.1
  6. Removedv1.4.3
  7. First observedv1.3.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only indicate readOnlyHint=false and destructiveHint=false, but the description discloses much more: file type/size restrictions, rejection of hidden files or paths outside the upload directory, the requirement to only upload user-chosen files, and the confirmation flow with preview/confirmToken. It also notes the return of the uploaded image URL. This is strong behavioral transparency beyond structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and front-loaded, but it is a single long paragraph with several compound sentences. While every sentence carries important information, the structure could be improved with line breaks or bullets for readability. It earns a 4 rather than 5 because it sacrifices light skimmability for completeness.

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?

Given the tool's complexity (4 optional parameters, no output schema, minimal annotations), the description covers all necessary operating context: filesystem sharing condition, upload directory constraints, security rule (user-chosen file only), confirmation flow, and return value. It even references MCP_CONFIRM_MODE for clients needing the fallback. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is 100%, the description adds crucial semantic context: the path/fileData selection rule, relative path resolution against VIBO_UPLOAD_DIR, allowed image formats, size limit, the filename default, and the exclusive two-step confirmToken semantics. It explains not just what each parameter is but when and how to use it correctly.

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 opens with a precise verb and resource: 'Set your Vibo profile photo from an image.' It immediately distinguishes this from the many sibling tools (events, songs, notifications) by naming the specific resource (profile photo). It also clarifies the two input modes (path vs fileData), making the tool's purpose unambiguous.

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?

The description gives explicit conditional guidance: 'Pass a local file path if the server shares your filesystem; otherwise pass the image bytes as base64 fileData.' It specifies valid image types, size limit, upload directory rules, and when to use confirmToken for two-step confirmation. This fully covers when and how to use the tool without leaving the agent to infer from schema alone.

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

Deploy Server

Other Tools