find_event_recommendations
Discover personalized event recommendations by searching for performers, events, or locations. Use geo-location, coordinates, or postal codes to find nearby events, with optional date filters and pagination.
Instructions
Get personalized event recommendations based on performers, events, or location. This tool first searches for performers and/or events based on the query (q parameter), then uses the IDs to find similar events. Use location parameters (geoip, lat/lon, postal_code) for nearby events.
Input Schema
Name | Required | Description | Default |
---|---|---|---|
end_utc | No | End date filter in ISO8601 UTC format (YYYY-MM-DD). Use with start_utc to define date ranges. | |
format | No | Output format. Use "structured" for readable format (default) or "json" for raw API response. Only use "json" if explicitly requested. | structured |
geoip | No | Use IP geolocation to provide recommendations for events near the user. | |
lat | No | Latitude coordinate for location-based recommendations. Use with lon and optionally range. | |
lon | No | Longitude coordinate for location-based recommendations. Use with lat and optionally range. | |
page | No | Page number for pagination. Default is 1. | |
per_page | No | Number of results to return per page (1-50). Default is 10. | |
postal_code | No | Postal code for location-based recommendations. Use with country code for better accuracy. | |
q | No | Search query to find either an event or performer to base recommendations on. If provided, the system will first look up the event ID or performer ID/slug automatically. | |
range | No | Search radius for location-based recommendations (e.g., "50mi", "25km"). Use with lat/lon or postal_code. | |
start_utc | No | Start date filter in ISO8601 UTC format (YYYY-MM-DD). Use for date ranges like "next month" or "this weekend". |
Input Schema (JSON Schema)
{
"$schema": "http://json-schema.org/draft-07/schema#",
"additionalProperties": false,
"properties": {
"end_utc": {
"description": "End date filter in ISO8601 UTC format (YYYY-MM-DD). Use with start_utc to define date ranges.",
"type": "string"
},
"format": {
"default": "structured",
"description": "Output format. Use \"structured\" for readable format (default) or \"json\" for raw API response. Only use \"json\" if explicitly requested.",
"enum": [
"structured",
"json"
],
"type": "string"
},
"geoip": {
"description": "Use IP geolocation to provide recommendations for events near the user.",
"type": "boolean"
},
"lat": {
"description": "Latitude coordinate for location-based recommendations. Use with lon and optionally range.",
"type": "number"
},
"lon": {
"description": "Longitude coordinate for location-based recommendations. Use with lat and optionally range.",
"type": "number"
},
"page": {
"default": 1,
"description": "Page number for pagination. Default is 1.",
"minimum": 1,
"type": "number"
},
"per_page": {
"default": 10,
"description": "Number of results to return per page (1-50). Default is 10.",
"maximum": 50,
"minimum": 1,
"type": "number"
},
"postal_code": {
"description": "Postal code for location-based recommendations. Use with country code for better accuracy.",
"type": "string"
},
"q": {
"description": "Search query to find either an event or performer to base recommendations on. If provided, the system will first look up the event ID or performer ID/slug automatically.",
"type": "string"
},
"range": {
"description": "Search radius for location-based recommendations (e.g., \"50mi\", \"25km\"). Use with lat/lon or postal_code.",
"type": "string"
},
"start_utc": {
"description": "Start date filter in ISO8601 UTC format (YYYY-MM-DD). Use for date ranges like \"next month\" or \"this weekend\".",
"type": "string"
}
},
"type": "object"
}