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, filter by host or guest, page through results, and choose compact or full member details including emails and avatars.

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

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.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight here: it discloses paging semantics (limit/skip apply per group), the merged response keys ({hosts, guests, hostsCount, guestsCount}), and the default-vs-full projection behavior. It does not state auth requirements or rate limits, but the paging and projection disclosure goes well beyond the annotations.

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?

One tight paragraph, front-loaded with the operation and its two modes, followed by response-shape detail. The parenthetical response keys are dense but functional; no sentence is filler.

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?

There is no output schema, yet the description names the exact return keys, explains what each view returns and what compact drops, and clarifies paging scope — everything an agent needs to invoke and interpret the call correctly.

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 description coverage is 100%, and the schema's view and limit entries already document the compact/full projection and per-group paging, so the description largely restates them. It adds only mild cross-parameter framing (the interaction between usersType and limit/skip), which justifies the baseline 3 rather than more.

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 and resource ("List the hosts and guests on an event") and immediately scopes it with the usersType behavior. An agent can distinguish it from sibling listing tools such as vibo_list_events or vibo_invite_users without reading any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the two calling modes (no usersType = merged groups, usersType = one group's page), which is genuine usage guidance. However, it never names an alternative sibling or says when this tool should be preferred over e.g. vibo_get_event or vibo_invite_users, so routing guidance is only implied.

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