Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_list_event_users

Read-only

List hosts and guests on an event, optionally filtering by host or guest type. Use counts to see group sizes, and paginate results per group or for a filtered page.

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.

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 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.
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 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"
+}
  2. Addedv1.5.3
  3. Removedv1.4.3
  4. First observedv1.3.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description reveals important behavior: the default merged response shape, the per-group pagination behavior, and the different behavior when usersType is supplied. This gives the agent a concrete mental model of what will happen without needing to call the tool.

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 carry the essential behavior, response shape, and conditional pagination rules with no wasted words. The key call distinction is front-loaded in the first sentence.

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?

Despite having no output schema, the description explains the default return shape and the usersType variant, while the input schema fully documents all five parameters. Combined with the readOnlyHint annotation, this is sufficient for an agent to select and call the tool correctly.

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?

Input schema coverage is 100%, so the baseline is 3. The description adds real semantic value by explaining how usersType changes the response and that limit/skip apply per group when usersType is omitted, which is more than the individual parameter descriptions convey.

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 specific verb and resource: 'List the hosts and guests on an event.' It adds conditional detail about the usersType parameter, making the tool's scope unambiguous and easily distinguishable from the many list-oriented siblings such as vibo_list_events or vibo_list_section_questions.

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 clearly conveys when to use the tool: to list event attendees, with an explicit fork for all users versus host-or-guest filtering. It does not name a particular sibling as an alternative or give exclusion criteria, but no sibling directly competes with this resource, so the usage context is clear enough.

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