Stats
Actions
Tags
From xp-mcp
Get full details for an XP event (venue, performers, price range, alert link)
How this command is triggered — by the user, by Claude, or both
Slash command
/xp-mcp:event-info <event name or id>The summary Claude sees in its command listing — used to decide when to auto-load this command
The user wants full details on: **$ARGUMENTS** Use the XP MCP `xp` server. 1. If the argument looks like an `event_id` (numeric or slug-shaped, no spaces, returned previously by `search_events`), call `get_event_details(event_id=<id>)` directly. Otherwise call `search_events` first to resolve the id, then `get_event_details`. 2. Present: - Event title + date + venue name + city - Performers (with role if multiple) - Price range (convert cents → dollars, include `$` symbol) - Image URL if returned - Price-alert URL if present 3. If the user asks about the venue specifically ...
The user wants full details on: $ARGUMENTS
Use the XP MCP xp server.
event_id (numeric or slug-shaped, no spaces, returned previously by search_events), call get_event_details(event_id=<id>) directly. Otherwise call search_events first to resolve the id, then get_event_details.$ symbol)get_venue_details(venue_id=<id>) and surface that.Do not fabricate fields the tool did not return. Voice: warm, plainspoken, fan-first.
npx claudepluginhub blpt-hngr/xp-claude-plugins --plugin xp-mcp