vibo_create_event_contact
Add a host or guest contact to an event by name, email, or phone, with a confirmation step before saving.
Instructions
Add a contact (host or guest) to an event with their name/email/phone. 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).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"eventId": "<eventId>",
"role": "<role>",
"email": "<email>"
},
"name": "vibo_create_event_contact"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| role | Yes | The contact's role in the event. | |
| Yes | Contact email (required by Vibo). | ||
| eventId | Yes | Event id. | |
| lastName | No | ||
| firstName | No | ||
| phoneCode | No | Country calling code, e.g. "1". | |
| phoneNumber | No | ||
| confirmToken | No | 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. |