Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_list_event_users

Read-only

List hosts and guests for an event, with optional filtering by host/guest type, pagination, and compact or full detail views.

Instructions

List the hosts and guests on an event. With no usersType, returns both groups merged ({hosts, guests, hostsCount, guestsCount}) and limit/skip apply per group; with usersType, returns that one group's page. Default (compact) view returns each member's id, name and role only; pass view:'full' for email addresses and avatars.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of items to skip, for paging (default 0).
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact (default) returns each member as {_id, firstName, lastName, role} only — no email addresses or avatar URLs; "full" returns Vibo's payload untouched, emails included. This document's field list is fixed by its query, so the projection cannot drop an unknown field.
limitNoMax items to return (default 20). Applies per group when usersType is omitted.
eventIdYesEvent id.
usersTypeNoFilter to only hosts or only guests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.1
    • changedInput schema / properties / view / description
      Previous value: -"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Vibo's payload untouched. No field projection: this server has no verified record of which Vibo fields matter, and inventing one would risk dropping a field a caller needs."New value: +"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact (default) returns each member as {_id, firstName, lastName, role} only — no email addresses or avatar URLs; \"full\" returns Vibo's payload untouched, emails included. This document's field list is fixed by its query, so the projection cannot drop an unknown field."
  2. 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"
  3. Changed1 schema field changedv1.8.0
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Vibo's payload untouched. No field projection: this server has no verified record of which Vibo fields matter, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  4. Addedv1.5.3
  5. Removedv1.4.3
  6. First observedv1.3.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description adds meaningful behavior: per-group pagination, merged vs. single-group return, and the difference between compact and full views. A minor inaccuracy exists ('id, name and role' vs. the schema's '_id, firstName, lastName, role'), but this does not contradict the annotations and overall behavior is well disclosed.

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 sentences, front-loaded with the main action, and each clause carries essential information (modes, pagination, view options). No wasted words.

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 read-only tool with no output schema, the description covers all key aspects: return structure for both modes, pagination behavior, and view options. It is complete enough for an agent to call it correctly without opening the schema.

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 baseline is 3. The description adds value by explaining that limit/skip apply per group when usersType is omitted and what usersType does, going beyond the schema's basic 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?

States a specific verb ('List') and resource ('hosts and guests on an event'), clearly distinguishing it from siblings like vibo_list_events (lists events) and vibo_get_event (gets event details). The purpose is unambiguous.

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 clear context on how to use the tool by explaining the two modes (with/without usersType) and the view parameter. However, it does not explicitly mention when not to use it or name alternative tools, so guidance on choosing between siblings is implicit rather than explicit.

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