What's Up In: local events
Server Details
Read-only search of upcoming local events worldwide: music, comedy, AI/tech, arts, food, sports.
- Status
- Healthy
- Uptime
- 100.0% over 23 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
The tools split cleanly along resource+scope lines: get_city vs list_cities (one city's counts vs. all cities), get_event vs search_events (detail by id vs. query), search_events vs list_upcoming (search words vs. wordless day-by-day browse). The main soft spot is search_across_cities, which only indexes 'travel-worthy' events, a boundary an agent could easily misjudge and use when it really wanted search_events; get_city vs list_cities also requires reading the descriptions to separate.
Every name is snake_case verb_noun with a small, predictable verb set: get_*, list_*, search_*. The only wrinkle is list_upcoming (no explicit noun object), which is still immediately readable and consistent with the rest.
Six tools is well within the sweet spot and each covers a distinct slice (city metadata, city list, single-city search, cross-city search, browse, event detail). No tool looks redundant or bolted on.
For a read-only events index the lifecycle is covered: discover cities, inspect coverage, search or browse, then fetch full details with sources. Gaps are minor: no pagination offset (agents are told to narrow instead), no direct venue/organizer lookup, and residencies are reachable only through the cross-city tool.
Available Tools
6 toolsget_cityGet one city's coverageARead-onlyIdempotentInspect
Get what one What's Up In city covers: how many upcoming events it lists and for which dates, when its data was last published, how many sources feed it, and upcoming events per category, topic, neighborhood and town. Call it before searching a city to pick valid category, topic, neighborhood and town values, or to tell a user what that city covers; it returns counts only, no events (use search_events or list_upcoming for those, list_cities for every city at once). No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list. |
Output Schema
| Name | Required | Description |
|---|---|---|
| mcp | No | |
| city | Yes | |
| name | No | |
| site | No | |
| metro | No | |
| towns | No | Upcoming events per town, the busiest first (search_events `town`) |
| topics | No | Upcoming events per topic (search_events `topic`) |
| regions | No | |
| coverage | No | Coverage and accuracy page |
| timezone | No | |
| last_date | No | |
| categories | No | Upcoming events per category (search_events `category`) |
| first_date | No | |
| attribution | No | |
| free_events | No | |
| neighborhoods | No | Upcoming events per neighborhood (the `neighborhood` argument) |
| data_generated | No | When this city's data was last published |
| upcoming_events | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: counts only with no event payloads, no sign-in required, and concrete rate limits (30 calls/minute, 2,500 event rows/hour). Rate limits and the no-events constraint are not derivable from any structured field.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with what the tool returns before routing advice and caveats. The second sentence is a dense run-on packing alternatives, exclusion, and rate limits, which slightly hurts scannability, but every clause carries information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists, yet the description still characterizes the shape of the response as counts-only, and it covers auth, limits, and sibling routing for a single-parameter tool. An agent has everything needed to call it correctly and interpret the result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the city parameter already lists every valid value, so the description adds no new parameter meaning beyond the schema. Baseline 3 applies since the schema does all the work here.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names a specific verb and resource ("Get what one What's Up In city covers") and enumerates exactly what comes back: event counts, date span, last-published date, source count, and per-category/topic/neighborhood/town breakdowns. It also distinguishes itself from siblings by stating it returns counts only, unlike search_events and list_upcoming.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit when-to-use ("Call it before searching a city to pick valid category, topic, neighborhood and town values, or to tell a user what that city covers") plus when-not-to and which alternative to reach for (search_events, list_upcoming, list_cities). Nothing about the routing decision is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_eventGet one eventARead-onlyIdempotentInspect
Get the full listing for one upcoming event by the id that search_events or list_upcoming returned, passing the same city it came from: title, dates, venue, price (all-in, or "See tickets"), the original listing (link), every source that lists it and first_seen / last_seen / last_fetched dates. Ids stay the same while an event is listed; a past or removed event returns an error, so search again. (search_across_cities results carry on_site links instead.) No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | 12-character event id | |
| city | Yes | Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list. |
Output Schema
| Name | Required | Description |
|---|---|---|
| city | Yes | |
| site | No | |
| event | Yes | |
| coverage | No | Coverage and accuracy page |
| attribution | No | |
| data_generated | No | When this city's data was last published |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, non-destructive, so the description correctly spends its budget on what annotations can't say: id stability while listed, an error on past or removed events, no sign-in requirement, and concrete rate limits (30 calls/min, 2,500 rows/hour). The only thing not disclosed is pagination/row-limit behavior for the response itself, which slightly caps the score.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the action and the id provenance, then return contents, then failure behavior, then limits — a sensible ordering. The parenthetical asides interrupt the main clause slightly and one sentence packs title/dates/venue/price/sources together, but nothing is redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Two required params, an output schema, and rich annotations are all complemented: provenance of the id, required city pairing, error behavior, auth status, and rate limits. An agent has everything needed to call it correctly and to recover from the documented failure mode.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a 12-character id and a full city list, so the schema does the heavy lifting. The description still adds genuine semantics beyond it: the `id` must be one returned by search_events or list_upcoming, and `city` must match the city the id came from, which is a coupling constraint absent from the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get the full listing for one upcoming event') and pins the identifier source to siblings search_events or list_upcoming. It even carves out the sibling whose results can't be used (search_across_cities carries `on_site` links), so an agent can separate it from all five siblings without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use it (id returned by search_events/list_upcoming, passing the same `city`), when it won't apply (search_across_cities results), and what to do on failure (past or removed event errors, so search again). That is a complete use/exclude/recovery loop.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_citiesList citiesARead-onlyIdempotentInspect
List every city What's Up In covers, with its site, its own MCP endpoint, its status (live or beta) and how many travel-worthy events it indexes now. Call it to find valid city values for search_events, list_upcoming, get_event and get_city, or names for search_across_cities' cities; for one city's neighborhoods, topics and event counts use get_city. Takes no arguments; the list changes only when a city launches. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| cities | Yes | |
| attribution | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, but the description adds context beyond them: no arguments required, no sign-in, a change cadence ('the list changes only when a city launches' – useful for caching), and concrete rate limits (30 calls/min, 2,500 event rows/hr). This is exactly the extra behavioral detail annotations cannot convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with what the tool returns, then usage, then operational constraints, in three dense sentences with no wasted clauses. The enumeration of returned fields is informative rather than filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, yet the description still summarizes the entry fields; combined with auth, rate limits, argument count, and the sibling routing, an agent has everything needed to call it correctly and interpret results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters (schema coverage 100%), so the baseline is 4; the description confirms this explicitly with 'Takes no arguments,' which prevents an agent from guessing at filters. There is no parameter syntax to add meaning to.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource (list every city) and enumerates exactly what each entry contains: site, MCP endpoint, status (live or beta), and current event count. It also names the sibling tools it complements and contrasts with get_city, so an agent can distinguish it without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit positive routing ('Call it to find valid `city` values for search_events, list_upcoming, get_event and get_city, or names for search_across_cities' `cities`') and an explicit alternative for the adjacent need ('for one city's neighborhoods, topics and event counts use get_city'). Nothing is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_upcomingList upcoming events in one cityARead-onlyIdempotentInspect
Browse the next N days of events in one What's Up In city, day by day, with no search words. by_day counts every match per date, and when more events match than limit the rows are spread evenly across the days, so each day is represented. Use it for overviews like "what's happening in this week"; for search words, free-only, a town or exact from/to dates use search_events, and for one event's details get_event. Optional filters: one category or topic, and a place: neighborhood keeps events inside a named area (radius_km widens it past the boundary), near ranks events by distance from a place or "lat,lon" within radius_km. get_city lists valid neighborhood names. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list. | |
| days | No | Window in days (default 7) | |
| near | No | Events within radius_km of a place in the city: a neighborhood, a town, a venue name, or "lat,lon". Results get distance_km, nearest first within each day. | |
| limit | No | Max rows (default 50) | |
| topic | No | ||
| category | No | ||
| radius_km | No | Distance for near (default 1.5, max 50), or how far neighborhood reaches past its boundary (default 0) | |
| neighborhood | No | Only events in this neighborhood or town of the city, e.g. 'Capitol Hill', 'Silver Lake', 'Cambridge'. Events whose venue isn't mapped can't be placed and are left out (place.unplaced_events counts them). | |
| changed_since | No | Only events added or changed (title, date or time, venue, link, price, sold out, status) at or after this moment: YYYY-MM-DD (the city's local date) or an ISO date-time. To follow up later, pass the previous result's changes.synced_at; changes.removed then lists events taken down since. |
Output Schema
| Name | Required | Description |
|---|---|---|
| city | Yes | |
| note | No | |
| site | No | |
| count | Yes | Events that matched in total |
| place | No | |
| shown | Yes | Events returned (at most limit) |
| by_day | No | Matches per date (YYYY-MM-DD), all of them, not just the rows shown |
| events | Yes | |
| changes | No | Only with changed_since |
| coverage | No | Coverage and accuracy page |
| attribution | No | |
| briefing_url | No | The dated weekly briefing for this week or next (counts plus picks per kind of event, #lane when the filters match one); null further out. Cite it for "what's on this week" |
| data_generated | No | When this city's data was last published |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnly/idempotent/non-destructive, but the description adds behavior they cannot express: the even spread of rows across days when matches exceed 'limit', the by_day counting rule, the unplaced-venue exclusion, and concrete quotas (30 calls/minute, 2,500 rows/hour) with no sign-in. These are the constraints an agent needs to plan paging and avoid repeat calls.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core behavior before routing and filters, and no filler. It is dense to the point of being a single long block, which slightly hurts scannability, but essentially every clause carries operational information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema and full annotations present, the description covers what remains: scope, alternatives, filter interactions, quirks, and rate limits. The only minor omission is any hint about changed_since follow-up semantics, which the schema carries instead.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 78% and already documents each parameter, but the description adds the cross-parameter rule that matters most: how 'limit' interacts with 'days' (rows spread evenly so each day is represented). It also clarifies the dual role of radius_km and the neighborhood vs near distinction, though it leaves enum values (topic/category) entirely to the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Browse the next N days of events in one What's Up In city, day by day') plus the key scope constraint ('with no search words'), which is exactly what separates it from search_events. An agent can distinguish it from all five siblings without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit use case ('what's happening in <city> this week') and routes three alternatives by condition: search words/free-only/town/exact dates to search_events, single-event details to get_event, and valid neighborhood names to get_city. Both inclusion and exclusion guidance are present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_across_citiesSearch events across all citiesARead-onlyIdempotentInspect
Search upcoming travel-worthy events in every What's Up In city at once: where an artist, band, comedian or team is playing, which cities have a festival, conference or expo, big arena shows, games and races. Only events worth a trip are indexed (named performers, festivals, conferences/expos, arena shows, games, races), not every local listing: for everything in one city (small gigs, classes, meetups) use search_events with its city. Kind residency also searches a worldwide list of residencies (pop-up cities, hacker houses, founder and research residencies, fellowship cohorts; most outside our cities, e.g. Kobe or Goa; in person, hybrid or remote; fixed dates, a start only, or rolling intake), each with its application details. Give a query, at least one of kinds, or a place. Each result names its city and links to the original listing (link) and the event on that city's site (on_site); searched says which cities were included and how fresh each is. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | YYYY-MM-DD, optional | |
| from | No | YYYY-MM-DD, default today | |
| near | No | "lat,lon": only events within radius_km of it, with distance_km. (search_events also takes place names.) Unmapped venues are left out (place.unplaced_events). | |
| kinds | No | Only these kinds: act = named performers; festival = festival; major = major local festival; conference = conference / expo; big_show = arena or amphitheater show; game = sports game (any level); pro_game = professional sports game (MLB, NFL, NBA, NHL, MLS, WNBA, NWSL); race = race; residency = residency, pop-up city, hacker house or fellowship cohort, worldwide (most are outside our cities); in person, hybrid or remote, fixed dates or rolling intake: see each result's residency.attendance and residency.schedule. | |
| limit | No | Default 50 | |
| query | No | An artist, band, comedian, team, festival or conference name, or words to match in titles/performers/venues, e.g. 'Khruangbin', 'Oktoberfest', 'AI summit'. Optional when `kinds`, `neighborhood` or `near` is given. | |
| cities | No | Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. Default: all. | |
| radius_km | No | Radius for near (default 10, max 200) | |
| trip_only | No | Only events worth a special trip (multi-day festivals, festivals on a city's watchlist, arena/amphitheater shows, multi-day conferences, full-distance races). Default: true when there is no query, false when searching a name. | |
| neighborhood | No | Only events in this neighborhood or town (whole words, e.g. 'Silver Lake', 'South End', 'Pasadena'). Events whose venue isn't mapped can't be placed and are left out; place.unplaced_events counts them. |
Output Schema
| Name | Required | Description |
|---|---|---|
| to | No | |
| from | No | |
| count | Yes | |
| place | No | |
| query | No | |
| shown | Yes | |
| events | Yes | |
| searched | No | Which cities were searched and how fresh each is |
| in_cities | No | |
| attribution | No | |
| looser_matches | No | Weaker matches left out (the query only in a title or venue) |
| residencies_worldwide | No | The worldwide residencies list the `residency` kind also searches |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already establish read-only, idempotent, non-destructive behavior, but the description adds substantial operational context: no sign-in, a 30 calls/minute limit, a 2,500 event-rows/hour limit, indexing restricted to trip-worthy events, and omission of unmapped venues for near/neighborhood searches. It also describes result metadata such as link, on_site, and searched freshness. These details go well beyond the annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single dense paragraph but front-loads the core purpose and the main alternative, search_events. It repeats some indexing scope details, but for a 10-parameter cross-city search tool the density is mostly justified. Better paragraph breaks or bullets would improve scanability, but little text is truly wasteful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity, 10 parameters, and the existence of an output schema, the description is highly complete. It covers indexing scope, single-city alternative, residency behavior, required call shape, result fields, and rate limits. An agent should be able to decide when and how to call it without needing further documentation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already carries the per-parameter semantics, including kinds, cities, near, radius_km, trip_only, and neighborhood. The description adds a useful cross-parameter validity rule ('Give a query, at least one of kinds, or a place') and some context around trip_only defaults. However, most parameter meaning is already present in the schema, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: searching upcoming travel-worthy events across every What's Up In city at once. It clearly distinguishes this from search_events by naming the sibling and explaining that search_events is for everything in one city. The kinds and scope are concrete enough for an agent to choose this tool confidently.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says when to use this tool versus search_events: use this for cross-city, trip-worthy events, and use search_events for all local listings in one city. It also states the minimum input condition ('Give a query, at least one of kinds, or a place') and explains the special residency scope. This is unusually clear routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_eventsSearch events in one cityARead-onlyIdempotentInspect
Search every upcoming event in one What's Up In city by words, dates, price, topic or place: music, dance, AI/tech, arts, comedy, food, sports, classes, volunteering, street fairs. Use it whenever the question has search words, a date range ("this weekend": from/to), free-only, a town or an area; for a day-by-day overview of the next few days with no search words use list_upcoming, and for an artist, festival or conference in several cities use search_across_cities. Words in query match the title, venue, performers, organizer or tags at the start of a word, singular or plural, with common synonyms; by default all must match, with match "any" (or | / commas between them) any one does; a misspelled word is read as the closest word the events use, and search in the result says how the query was read. Dates are the city's local dates. Results come earliest first, at most limit; count says how many matched in total, so narrow the search rather than paging. Each event has its original listing (link) and an id for get_event. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Latest date, YYYY-MM-DD (default: none) | |
| city | Yes | Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list. | |
| free | No | Only free events | |
| from | No | Earliest date, YYYY-MM-DD (default: today) | |
| near | No | Events within radius_km of a place in the city: a neighborhood, a town, a venue name, or "lat,lon". Results get distance_km, nearest first within each day. | |
| town | No | Only events in this town or city within the metro, e.g. 'Oakland', 'Pasadena' (case-insensitive) | |
| limit | No | Max results (default 25) | |
| match | No | all (default): every word must match; any: at least one word or |-separated phrase does | |
| query | No | Free text, e.g. 'salsa', 'hackathon', 'street fair', an artist or venue. Alternatives: 'salsa | bachata'; a phrase: quotes. A neighborhood or town after 'in'/'near' becomes the place filter. | |
| topic | No | Topic, e.g. comedy, film, food_drink, sports, talks, classes, markets, outdoors | |
| category | No | Scored category | |
| radius_km | No | Distance for near (default 1.5, max 50), or how far neighborhood reaches past its boundary (default 0) | |
| neighborhood | No | Only events in this neighborhood or town of the city, e.g. 'Capitol Hill', 'Silver Lake', 'Cambridge'. Events whose venue isn't mapped can't be placed and are left out (place.unplaced_events counts them). | |
| changed_since | No | Only events added or changed (title, date or time, venue, link, price, sold out, status) at or after this moment: YYYY-MM-DD (the city's local date) or an ISO date-time. To follow up later, pass the previous result's changes.synced_at; changes.removed then lists events taken down since. |
Output Schema
| Name | Required | Description |
|---|---|---|
| city | Yes | |
| site | No | |
| count | Yes | Events that matched in total |
| place | No | |
| shown | Yes | Events returned (at most limit) |
| events | Yes | |
| search | No | How the query was read |
| changes | No | Only with changed_since |
| coverage | No | Coverage and accuracy page |
| attribution | No | |
| briefing_url | No | The dated weekly briefing for this week or next (counts plus picks per kind of event, #lane when the filters match one); null further out. Cite it for "what's on this week" |
| data_generated | No | When this city's data was last published |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered; the description adds operationally valuable context beyond that: no sign-in required, rate limits of 30 calls/minute and 2,500 event rows/hour, earliest-first ordering, and the key advice that `count` reports total matches so you should narrow the search rather than page. It also discloses fuzzy-matching behavior (misspellings resolved to the closest known word, echoed back in `search`), which is non-obvious and would otherwise surprise an agent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a single dense paragraph, but it is front-loaded with purpose and disambiguation before query syntax and rate limits, and nearly every clause carries actionable information. A few items (the full topic enumeration in prose) partially duplicate the schema enums and could be trimmed without loss.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 14-parameter search tool with an output schema, the description covers everything an agent needs: when to use it versus siblings, how queries are interpreted, date locality, ordering and limit behavior, the count/narrow-don't-page rule, and how to follow up on individual results via `id`/get_event and `changes.synced_at`. The output schema handles return shape, so nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3; the description goes further by explaining match semantics that the schema does not — words match title/venue/performers/organizer/tags at word start, singular or plural, with common synonyms, `match: all` as default and `any` accepting | or comma-separated alternatives, and that dates are the city's local dates. That materially changes how an agent should phrase queries and interpret `from`/`to`.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
"Search every upcoming event in one What's Up In city" gives a specific verb, resource, and scope, then enumerates the content domains it covers (music, dance, AI/tech, arts, comedy, food, sports...). It explicitly names what it is not (list_upcoming, search_across_cities), so an agent can route without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It states the positive trigger conditions (search words, a date range like "this weekend" as from/to, free-only, a town or area) and names two alternatives with the exact conditions that select them: day-by-day overview without search words → list_upcoming; multi-city artist/festival/conference → search_across_cities. When-not guidance is explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
5 tool updates
- Changed
get_city1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list."
- Changed
get_event2 fields changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list." - added
Output schema / properties / event / properties / new_hostAdded value: +{ + "description": "True when the event's organizer, group or promoter first appeared in our listings within the last two weeks; a plain discovery marker, not a quality signal. Absent otherwise", + "type": "boolean" +}
- Changed
list_upcoming2 fields changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list." - added
Output schema / properties / events / items / properties / new_hostAdded value: +{ + "description": "True when the event's organizer, group or promoter first appeared in our listings within the last two weeks; a plain discovery marker, not a quality signal. Absent otherwise", + "type": "boolean" +}
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. Default: all."
- Changed
search_events2 fields changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Paris, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list." - added
Output schema / properties / events / items / properties / new_hostAdded value: +{ + "description": "True when the event's organizer, group or promoter first appeared in our listings within the last two weeks; a plain discovery marker, not a quality signal. Absent otherwise", + "type": "boolean" +}
5 tool updates
- Changed
get_city1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list."
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list."
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. Default: all."
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Dubai, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Tokyo, Toronto. list_cities has the full list."
5 tool updates
- Changed
get_city1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. list_cities has the full list."
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. list_cities has the full list."
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. Default: all."
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Austin, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, New York, Philadelphia, Phoenix, Portland, Salt Lake City, San Antonio, Toronto. list_cities has the full list."
5 tool updates
- Changed
get_city1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. list_cities has the full list."
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. list_cities has the full list."
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. Default: all."
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City, Toronto. list_cities has the full list."
5 tool updates
- Changed
get_city1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."
- Changed
get_event2 fields changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list." - added
Output schema / properties / event / properties / venue_statusAdded value: +{ + "description": "Present only when location is empty, and says why (we never guess a venue): rsvp = the address is shared after RSVP/registration; tba = the venue isn't decided; hidden = the source shows the venue to its members only (Meetup stubs; /mcp leaves these out, so you won't see it here); title = the title names the place; text = the description names a place; unset = the host left it blank. Open the link for the venue", + "enum": [ + "rsvp", + "tba", + "hidden", + "title", + "text", + "unset" + ], + "type": "string" +}
- Changed
list_upcoming2 fields changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list." - added
Output schema / properties / events / items / properties / venue_statusAdded value: +{ + "description": "Present only when location is empty, and says why (we never guess a venue): rsvp = the address is shared after RSVP/registration; tba = the venue isn't decided; hidden = the source shows the venue to its members only (Meetup stubs; /mcp leaves these out, so you won't see it here); title = the title names the place; text = the description names a place; unset = the host left it blank. Open the link for the venue", + "enum": [ + "rsvp", + "tba", + "hidden", + "title", + "text", + "unset" + ], + "type": "string" +}
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. Default: all."
- Changed
search_events2 fields changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list." - added
Output schema / properties / events / items / properties / venue_statusAdded value: +{ + "description": "Present only when location is empty, and says why (we never guess a venue): rsvp = the address is shared after RSVP/registration; tba = the venue isn't decided; hidden = the source shows the venue to its members only (Meetup stubs; /mcp leaves these out, so you won't see it here); title = the title names the place; text = the description names a place; unset = the host left it blank. Open the link for the venue", + "enum": [ + "rsvp", + "tba", + "hidden", + "title", + "text", + "unset" + ], + "type": "string" +}
5 tool updates
- Changed
get_city1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. Default: all."
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."
5 tool updates
- Changed
get_city1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
get_event2 fields changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list." - added
Output schema / properties / event / properties / changedAdded value: +{ + "description": "When we last saw the title, date or time, venue, link, price or status change (local ISO time); the first-seen day for older events", + "type": [ + "string", + "null" + ] +}
- Changed
list_upcoming6 fields changed- added
Input schema / properties / changed_sinceAdded value: +{ + "description": "Only events added or changed (title, date or time, venue, link, price, sold out, status) at or after this moment: YYYY-MM-DD (the city's local date) or an ISO date-time. To follow up later, pass the previous result's changes.synced_at; changes.removed then lists events taken down since.", + "type": "string" +} - changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list." - changed
Input schema / properties / topic / enumPrevious value: -[ - "arts", - "books", - "civic", - "classes", - "comedy", - "community", - "conferences", - "culture", - "faith", - "family", - "film", - "food_drink", - "games", - "markets", - "networking", - "nightlife", - "nonprofit", - "outdoors", - "science", - "sports", - "startup", - "talks", - "wellness", - "wine", - "business" -]New value: +[ + "arts", + "books", + "civic", + "classes", + "comedy", + "community", + "conferences", + "culture", + "faith", + "family", + "film", + "food_drink", + "games", + "markets", + "networking", + "nightlife", + "nonprofit", + "outdoors", + "science", + "sports", + "startup", + "talks", + "theater", + "wellness", + "wine", + "business", + "ai", + "tech", + "service_orgs" +] - added
Output schema / properties / briefing_urlAdded value: +{ + "description": "The dated weekly briefing for this week or next (counts plus picks per kind of event, #lane when the filters match one); null further out. Cite it for \"what's on this week\"", + "type": [ + "string", + "null" + ] +} - added
Output schema / properties / changesAdded value: +{ + "description": "Only with changed_since", + "properties": { + "note": { + "type": [ + "string", + "null" + ] + }, + "removed": { + "description": "Upcoming events taken down (cancelled, delisted or merged into another listing) since `since`, newest first, last two weeks at most", + "items": { + "properties": { + "date": { + "type": [ + "string", + "null" + ] + }, + "id": { + "type": "string" + }, + "removed": { + "type": "string" + }, + "title": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "id", + "removed" + ], + "type": "object" + }, + "type": "array" + }, + "removed_count": { + "description": "Total removals when more than are listed", + "type": "number" + }, + "since": { + "type": "string" + }, + "synced_at": { + "description": "Pass this as changed_since next time to get only what changed after this answer", + "type": [ + "string", + "null" + ] + }, + "tracked_since": { + "description": "When change tracking started for this city", + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "since", + "removed" + ], + "type": "object" +} - added
Output schema / properties / events / items / properties / changedAdded value: +{ + "description": "When we last saw the title, date or time, venue, link, price or status change (local ISO time); the first-seen day for older events", + "type": [ + "string", + "null" + ] +}
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all."
- Changed
search_events6 fields changed- added
Input schema / properties / changed_sinceAdded value: +{ + "description": "Only events added or changed (title, date or time, venue, link, price, sold out, status) at or after this moment: YYYY-MM-DD (the city's local date) or an ISO date-time. To follow up later, pass the previous result's changes.synced_at; changes.removed then lists events taken down since.", + "type": "string" +} - changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Colorado Springs & Pueblo, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list." - changed
Input schema / properties / topic / enumPrevious value: -[ - "arts", - "books", - "civic", - "classes", - "comedy", - "community", - "conferences", - "culture", - "faith", - "family", - "film", - "food_drink", - "games", - "markets", - "networking", - "nightlife", - "nonprofit", - "outdoors", - "science", - "sports", - "startup", - "talks", - "wellness", - "wine", - "business" -]New value: +[ + "arts", + "books", + "civic", + "classes", + "comedy", + "community", + "conferences", + "culture", + "faith", + "family", + "film", + "food_drink", + "games", + "markets", + "networking", + "nightlife", + "nonprofit", + "outdoors", + "science", + "sports", + "startup", + "talks", + "theater", + "wellness", + "wine", + "business", + "ai", + "tech", + "service_orgs" +] - added
Output schema / properties / briefing_urlAdded value: +{ + "description": "The dated weekly briefing for this week or next (counts plus picks per kind of event, #lane when the filters match one); null further out. Cite it for \"what's on this week\"", + "type": [ + "string", + "null" + ] +} - added
Output schema / properties / changesAdded value: +{ + "description": "Only with changed_since", + "properties": { + "note": { + "type": [ + "string", + "null" + ] + }, + "removed": { + "description": "Upcoming events taken down (cancelled, delisted or merged into another listing) since `since`, newest first, last two weeks at most", + "items": { + "properties": { + "date": { + "type": [ + "string", + "null" + ] + }, + "id": { + "type": "string" + }, + "removed": { + "type": "string" + }, + "title": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "id", + "removed" + ], + "type": "object" + }, + "type": "array" + }, + "removed_count": { + "description": "Total removals when more than are listed", + "type": "number" + }, + "since": { + "type": "string" + }, + "synced_at": { + "description": "Pass this as changed_since next time to get only what changed after this answer", + "type": [ + "string", + "null" + ] + }, + "tracked_since": { + "description": "When change tracking started for this city", + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "since", + "removed" + ], + "type": "object" +} - added
Output schema / properties / events / items / properties / changedAdded value: +{ + "description": "When we last saw the title, date or time, venue, link, price or status change (local ISO time); the first-seen day for older events", + "type": [ + "string", + "null" + ] +}
5 tool updates
- Changed
get_city1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
search_across_cities5 fields changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all." - changed
Input schema / properties / kinds / descriptionPrevious value: -"Only these kinds: act = named performers; festival = festival; major = major local festival; conference = conference / expo; big_show = arena or amphitheater show; game = sports game (any level); pro_game = professional sports game (MLB, NFL, NBA, NHL, MLS, WNBA, NWSL); race = race; residency = residency, pop-up city, hacker house or co-located fellowship, worldwide (4+ days in person; most are outside our cities)."New value: +"Only these kinds: act = named performers; festival = festival; major = major local festival; conference = conference / expo; big_show = arena or amphitheater show; game = sports game (any level); pro_game = professional sports game (MLB, NFL, NBA, NHL, MLS, WNBA, NWSL); race = race; residency = residency, pop-up city, hacker house or fellowship cohort, worldwide (most are outside our cities); in person, hybrid or remote, fixed dates or rolling intake: see each result's residency.attendance and residency.schedule." - added
Output schema / properties / events / items / properties / ongoingAdded value: +{ + "type": "boolean" +} - added
Output schema / properties / events / items / properties / residency / properties / attendanceAdded value: +{ + "description": "in_person, hybrid (in person with a remote option) or remote", + "type": [ + "string", + "null" + ] +} - added
Output schema / properties / events / items / properties / residency / properties / scheduleAdded value: +{ + "description": "fixed (start and end), start_only (no stated end) or rolling (ongoing intake; `date` is today)", + "type": [ + "string", + "null" + ] +}
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
5 tool updates
- Changed
get_city1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
search_across_cities5 fields changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all." - changed
Input schema / properties / kinds / descriptionPrevious value: -"Only these kinds: act = named performers; festival = festival; major = major local festival; conference = conference / expo; big_show = arena or amphitheater show; game = sports game (any level); pro_game = professional sports game (MLB, NFL, NBA, NHL, MLS, WNBA, NWSL); race = race."New value: +"Only these kinds: act = named performers; festival = festival; major = major local festival; conference = conference / expo; big_show = arena or amphitheater show; game = sports game (any level); pro_game = professional sports game (MLB, NFL, NBA, NHL, MLS, WNBA, NWSL); race = race; residency = residency, pop-up city, hacker house or co-located fellowship, worldwide (4+ days in person; most are outside our cities)." - changed
Input schema / properties / kinds / items / enumPrevious value: -[ - "act", - "festival", - "major", - "conference", - "big_show", - "game", - "pro_game", - "race" -]New value: +[ + "act", + "festival", + "major", + "conference", + "big_show", + "game", + "pro_game", + "race", + "residency" +] - added
Output schema / properties / events / items / properties / residencyAdded value: +{ + "description": "Residencies (kind `residency`): program details from its official page", + "properties": { + "application": { + "description": "open, rolling, closed, invite or unknown", + "type": [ + "string", + "null" + ] + }, + "apply_deadline": { + "description": "YYYY-MM-DD when the program states one", + "type": [ + "string", + "null" + ] + }, + "apply_url": { + "type": [ + "string", + "null" + ] + }, + "city": { + "type": [ + "string", + "null" + ] + }, + "cost": { + "description": "free, stipend, sponsored, paid or unknown (never a price)", + "type": [ + "string", + "null" + ] + }, + "country": { + "type": [ + "string", + "null" + ] + }, + "edition": { + "type": [ + "string", + "null" + ] + }, + "focus": { + "items": { + "type": "string" + }, + "type": "array" + }, + "kind": { + "description": "popup_city, hacker_house, founder_residency, research_residency, artist_residency, fellowship or other", + "type": [ + "string", + "null" + ] + }, + "program": { + "type": [ + "string", + "null" + ] + }, + "size": { + "type": [ + "string", + "null" + ] + }, + "summary": { + "type": [ + "string", + "null" + ] + }, + "tech": { + "type": "boolean" + } + }, + "required": [], + "type": "object" +} - added
Output schema / properties / residencies_worldwideAdded value: +{ + "description": "The worldwide residencies list the `residency` kind also searches", + "properties": { + "events": { + "type": "number" + }, + "indexed": { + "type": "boolean" + }, + "updated": { + "type": [ + "string", + "null" + ] + } + }, + "required": [], + "type": "object" +}
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Montreal, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
4 tool updates
- Changed
get_event2 fields changed- added
Output schema / properties / event / properties / event_statusAdded value: +{ + "description": "What a source says: postponed (no new date yet; listed on its original date), rescheduled (this is the new date), moved (to another venue; location is the new one), sold_out. Absent = scheduled as listed; cancelled events are left out", + "enum": [ + "sold_out", + "postponed", + "rescheduled", + "moved" + ], + "type": "string" +} - added
Output schema / properties / event / properties / status_noteAdded value: +{ + "description": "The source's own wording of event_status, e.g. \"Moved to The Warfield\"", + "type": "string" +}
- Changed
list_upcoming2 fields changed- added
Output schema / properties / events / items / properties / event_statusAdded value: +{ + "description": "What a source says: postponed (no new date yet; listed on its original date), rescheduled (this is the new date), moved (to another venue; location is the new one), sold_out. Absent = scheduled as listed; cancelled events are left out", + "enum": [ + "sold_out", + "postponed", + "rescheduled", + "moved" + ], + "type": "string" +} - added
Output schema / properties / events / items / properties / status_noteAdded value: +{ + "description": "The source's own wording of event_status, e.g. \"Moved to The Warfield\"", + "type": "string" +}
- Changed
search_across_cities1 field changed- added
Output schema / properties / events / items / properties / event_statusAdded value: +{ + "description": "sold_out, postponed, rescheduled or moved when a source says so (as in search_events)", + "type": [ + "string", + "null" + ] +}
- Changed
search_events2 fields changed- added
Output schema / properties / events / items / properties / event_statusAdded value: +{ + "description": "What a source says: postponed (no new date yet; listed on its original date), rescheduled (this is the new date), moved (to another venue; location is the new one), sold_out. Absent = scheduled as listed; cancelled events are left out", + "enum": [ + "sold_out", + "postponed", + "rescheduled", + "moved" + ], + "type": "string" +} - added
Output schema / properties / events / items / properties / status_noteAdded value: +{ + "description": "The source's own wording of event_status, e.g. \"Moved to The Warfield\"", + "type": "string" +}
5 tool updates
- Changed
get_city1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all."
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
5 tool updates
- Changed
get_city1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all."
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
1 tool update
- Changed
search_events3 fields changed- added
Input schema / properties / matchAdded value: +{ + "description": "all (default): every word must match; any: at least one word or |-separated phrase does", + "enum": [ + "all", + "any" + ], + "type": "string" +} - changed
Input schema / properties / query / descriptionPrevious value: -"Free text, e.g. 'salsa', 'hackathon', 'street fair', an artist or venue"New value: +"Free text, e.g. 'salsa', 'hackathon', 'street fair', an artist or venue. Alternatives: 'salsa | bachata'; a phrase: quotes. A neighborhood or town after 'in'/'near' becomes the place filter." - added
Output schema / properties / searchAdded value: +{ + "description": "How the query was read", + "properties": { + "match": { + "description": "all, any or semantic: how the query's words were combined", + "type": [ + "string", + "null" + ] + }, + "order": { + "description": "\"best match first\" for match semantic (otherwise results are earliest first)", + "type": [ + "string", + "null" + ] + }, + "place_from_query": { + "description": "A neighborhood or town taken from the query and used as the place filter", + "type": [ + "string", + "null" + ] + }, + "read_as": { + "additionalProperties": { + "type": "string" + }, + "description": "A word nothing matched, read as the closest word the events use", + "type": "object" + }, + "terms": { + "description": "Each word or phrase searched, with the other forms that counted (synonyms)", + "items": { + "properties": { + "also": { + "items": { + "type": "string" + }, + "type": "array" + }, + "term": { + "type": "string" + } + }, + "required": [], + "type": "object" + }, + "type": "array" + } + }, + "required": [], + "type": "object" +}
3 tool updates
- Changed
get_event1 field changed- added
Output schema / properties / event / properties / checked_liveAdded value: +{ + "description": "When we last opened the original listing and found it still matches (time, venue, not cancelled); local ISO time. Absent = not checked in the last two days", + "type": [ + "string", + "null" + ] +}
- Changed
list_upcoming1 field changed- added
Output schema / properties / events / items / properties / checked_liveAdded value: +{ + "description": "When we last opened the original listing and found it still matches (time, venue, not cancelled); local ISO time. Absent = not checked in the last two days", + "type": [ + "string", + "null" + ] +}
- Changed
search_events1 field changed- added
Output schema / properties / events / items / properties / checked_liveAdded value: +{ + "description": "When we last opened the original listing and found it still matches (time, venue, not cancelled); local ISO time. Absent = not checked in the last two days", + "type": [ + "string", + "null" + ] +}
2 tool updates
- Changed
list_upcoming1 field changed- changed
Input schema / properties / topic / enumPrevious value: -[ - "arts", - "books", - "civic", - "classes", - "comedy", - "community", - "conferences", - "culture", - "faith", - "family", - "film", - "food_drink", - "games", - "markets", - "networking", - "nightlife", - "nonprofit", - "outdoors", - "science", - "sports", - "startup", - "talks", - "wellness", - "wine" -]New value: +[ + "arts", + "books", + "civic", + "classes", + "comedy", + "community", + "conferences", + "culture", + "faith", + "family", + "film", + "food_drink", + "games", + "markets", + "networking", + "nightlife", + "nonprofit", + "outdoors", + "science", + "sports", + "startup", + "talks", + "wellness", + "wine", + "business" +]
- Changed
search_events1 field changed- changed
Input schema / properties / topic / enumPrevious value: -[ - "arts", - "books", - "civic", - "classes", - "comedy", - "community", - "conferences", - "culture", - "faith", - "family", - "film", - "food_drink", - "games", - "markets", - "networking", - "nightlife", - "nonprofit", - "outdoors", - "science", - "sports", - "startup", - "talks", - "wellness", - "wine" -]New value: +[ + "arts", + "books", + "civic", + "classes", + "comedy", + "community", + "conferences", + "culture", + "faith", + "family", + "film", + "food_drink", + "games", + "markets", + "networking", + "nightlife", + "nonprofit", + "outdoors", + "science", + "sports", + "startup", + "talks", + "wellness", + "wine", + "business" +]
6 tool updates
- Added
get_city - Changed
get_event2 fields changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "attribution": { + "type": "string" + }, + "city": { + "type": "string" + }, + "coverage": { + "description": "Coverage and accuracy page", + "type": [ + "string", + "null" + ] + }, + "data_generated": { + "description": "When this city's data was last published", + "type": [ + "string", + "null" + ] + }, + "event": { + "properties": { + "audience": { + "description": "kids, teens or seniors when the event is only for them", + "type": [ + "string", + "null" + ] + }, + "biz_formats": { + "items": { + "type": "string" + }, + "type": "array" + }, + "categories": { + "items": { + "type": "string" + }, + "type": "array" + }, + "city": { + "description": "Town or city within the metro", + "type": [ + "string", + "null" + ] + }, + "date": { + "description": "Local start date, YYYY-MM-DD", + "type": "string" + }, + "distance_km": { + "description": "With near: distance from the place", + "type": "number" + }, + "end": { + "type": [ + "string", + "null" + ] + }, + "first_seen": { + "type": [ + "string", + "null" + ] + }, + "free": { + "type": "boolean" + }, + "id": { + "description": "Stable 12-character id; pass it to get_event", + "type": "string" + }, + "last_fetched": { + "type": [ + "string", + "null" + ] + }, + "last_seen": { + "type": [ + "string", + "null" + ] + }, + "link": { + "description": "The original listing; keep it and credit What's Up In", + "type": [ + "string", + "null" + ] + }, + "location": { + "type": [ + "string", + "null" + ] + }, + "neighborhood": { + "type": [ + "string", + "null" + ] + }, + "performers": { + "items": { + "type": "string" + }, + "type": "array" + }, + "possibly_free": { + "type": "boolean" + }, + "posted_by_sources": { + "type": "number" + }, + "price": { + "description": "All-in price as the source states it, \"Free\", or \"See tickets\" when the source doesn't state the all-in total", + "type": [ + "string", + "null" + ] + }, + "recurring": { + "description": "weekly, biweekly or monthly when the event is one date of a series", + "type": [ + "string", + "null" + ] + }, + "region": { + "type": [ + "string", + "null" + ] + }, + "rv": { + "type": [ + "string", + "null" + ] + }, + "sectors": { + "items": { + "type": "string" + }, + "type": "array" + }, + "sold_out": { + "type": "boolean" + }, + "sources": { + "items": { + "type": "string" + }, + "type": "array" + }, + "start": { + "description": "Local start, ISO 8601, when the source gives a time", + "type": [ + "string", + "null" + ] + }, + "title": { + "type": "string" + }, + "topics": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "id", + "title", + "date" + ], + "type": "object" + }, + "site": { + "type": "string" + } + }, + "required": [ + "event", + "city" + ], + "type": "object" +}
- Changed
list_cities1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "attribution": { + "type": "string" + }, + "cities": { + "items": { + "properties": { + "city": { + "type": "string" + }, + "indexed": { + "type": "boolean" + }, + "mcp": { + "type": [ + "string", + "null" + ] + }, + "metro": { + "type": [ + "string", + "null" + ] + }, + "note": { + "type": [ + "string", + "null" + ] + }, + "site": { + "type": [ + "string", + "null" + ] + }, + "slug": { + "type": [ + "string", + "null" + ] + }, + "state": { + "type": [ + "string", + "null" + ] + }, + "status": { + "type": [ + "string", + "null" + ] + }, + "travel_events": { + "type": "number" + }, + "updated": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "city" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "cities" + ], + "type": "object" +}
- Changed
list_upcoming2 fields changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "attribution": { + "type": "string" + }, + "by_day": { + "additionalProperties": { + "type": "number" + }, + "description": "Matches per date (YYYY-MM-DD), all of them, not just the rows shown", + "type": "object" + }, + "city": { + "type": "string" + }, + "count": { + "description": "Events that matched in total", + "type": "number" + }, + "coverage": { + "description": "Coverage and accuracy page", + "type": [ + "string", + "null" + ] + }, + "data_generated": { + "description": "When this city's data was last published", + "type": [ + "string", + "null" + ] + }, + "events": { + "items": { + "properties": { + "audience": { + "description": "kids, teens or seniors when the event is only for them", + "type": [ + "string", + "null" + ] + }, + "biz_formats": { + "items": { + "type": "string" + }, + "type": "array" + }, + "categories": { + "items": { + "type": "string" + }, + "type": "array" + }, + "city": { + "description": "Town or city within the metro", + "type": [ + "string", + "null" + ] + }, + "date": { + "description": "Local start date, YYYY-MM-DD", + "type": "string" + }, + "distance_km": { + "description": "With near: distance from the place", + "type": "number" + }, + "end": { + "type": [ + "string", + "null" + ] + }, + "first_seen": { + "type": [ + "string", + "null" + ] + }, + "free": { + "type": "boolean" + }, + "id": { + "description": "Stable 12-character id; pass it to get_event", + "type": "string" + }, + "last_fetched": { + "type": [ + "string", + "null" + ] + }, + "last_seen": { + "type": [ + "string", + "null" + ] + }, + "link": { + "description": "The original listing; keep it and credit What's Up In", + "type": [ + "string", + "null" + ] + }, + "location": { + "type": [ + "string", + "null" + ] + }, + "neighborhood": { + "type": [ + "string", + "null" + ] + }, + "performers": { + "items": { + "type": "string" + }, + "type": "array" + }, + "possibly_free": { + "type": "boolean" + }, + "posted_by_sources": { + "type": "number" + }, + "price": { + "description": "All-in price as the source states it, \"Free\", or \"See tickets\" when the source doesn't state the all-in total", + "type": [ + "string", + "null" + ] + }, + "recurring": { + "description": "weekly, biweekly or monthly when the event is one date of a series", + "type": [ + "string", + "null" + ] + }, + "region": { + "type": [ + "string", + "null" + ] + }, + "rv": { + "type": [ + "string", + "null" + ] + }, + "sectors": { + "items": { + "type": "string" + }, + "type": "array" + }, + "sold_out": { + "type": "boolean" + }, + "sources": { + "items": { + "type": "string" + }, + "type": "array" + }, + "start": { + "description": "Local start, ISO 8601, when the source gives a time", + "type": [ + "string", + "null" + ] + }, + "title": { + "type": "string" + }, + "topics": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "id", + "title", + "date" + ], + "type": "object" + }, + "type": "array" + }, + "note": { + "type": [ + "string", + "null" + ] + }, + "place": { + "properties": { + "center": { + "items": { + "type": "number" + }, + "type": "array" + }, + "kind": { + "type": [ + "string", + "null" + ] + }, + "matched": { + "type": [ + "string", + "null" + ] + }, + "note": { + "type": [ + "string", + "null" + ] + }, + "radius_km": { + "type": [ + "number", + "null" + ] + }, + "unplaced_events": { + "description": "Events left out because their venue isn't mapped", + "type": "number" + } + }, + "required": [], + "type": "object" + }, + "shown": { + "description": "Events returned (at most limit)", + "type": "number" + }, + "site": { + "type": "string" + } + }, + "required": [ + "count", + "shown", + "events", + "city" + ], + "type": "object" +}
- Changed
search_across_cities2 fields changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "attribution": { + "type": "string" + }, + "count": { + "type": "number" + }, + "events": { + "items": { + "properties": { + "also_on": { + "items": { + "type": "string" + }, + "type": "array" + }, + "city": { + "type": "string" + }, + "city_site": { + "type": [ + "string", + "null" + ] + }, + "date": { + "type": "string" + }, + "distance_km": { + "type": "number" + }, + "end_date": { + "type": [ + "string", + "null" + ] + }, + "free": { + "type": "boolean" + }, + "id": { + "type": "string" + }, + "kinds": { + "items": { + "type": "string" + }, + "type": "array" + }, + "level": { + "type": [ + "string", + "null" + ] + }, + "link": { + "description": "The original listing", + "type": [ + "string", + "null" + ] + }, + "neighborhood": { + "type": [ + "string", + "null" + ] + }, + "on_site": { + "description": "The event on that city's site", + "type": [ + "string", + "null" + ] + }, + "performers": { + "items": { + "type": "string" + }, + "type": "array" + }, + "price": { + "type": [ + "string", + "null" + ] + }, + "start": { + "type": [ + "string", + "null" + ] + }, + "title": { + "type": "string" + }, + "town": { + "type": [ + "string", + "null" + ] + }, + "trip": { + "type": "boolean" + }, + "venue": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "id", + "title", + "date", + "city" + ], + "type": "object" + }, + "type": "array" + }, + "from": { + "type": [ + "string", + "null" + ] + }, + "in_cities": { + "type": "number" + }, + "looser_matches": { + "description": "Weaker matches left out (the query only in a title or venue)", + "type": "number" + }, + "place": { + "properties": { + "near": { + "items": { + "type": "number" + }, + "type": "array" + }, + "neighborhood": { + "type": [ + "string", + "null" + ] + }, + "note": { + "type": [ + "string", + "null" + ] + }, + "radius_km": { + "type": [ + "number", + "null" + ] + }, + "unplaced_events": { + "type": "number" + } + }, + "required": [], + "type": "object" + }, + "query": { + "type": [ + "string", + "null" + ] + }, + "searched": { + "description": "Which cities were searched and how fresh each is", + "items": { + "properties": { + "city": { + "type": "string" + }, + "events": { + "type": "number" + }, + "indexed": { + "type": "boolean" + }, + "note": { + "type": [ + "string", + "null" + ] + }, + "status": { + "type": [ + "string", + "null" + ] + }, + "updated": { + "type": [ + "string", + "null" + ] + } + }, + "required": [], + "type": "object" + }, + "type": "array" + }, + "shown": { + "type": "number" + }, + "to": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "count", + "shown", + "events" + ], + "type": "object" +}
- Changed
search_events2 fields changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Fresno, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Kansas City, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Raleigh, Richmond, Rome, Salt Lake City, San Antonio, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "attribution": { + "type": "string" + }, + "city": { + "type": "string" + }, + "count": { + "description": "Events that matched in total", + "type": "number" + }, + "coverage": { + "description": "Coverage and accuracy page", + "type": [ + "string", + "null" + ] + }, + "data_generated": { + "description": "When this city's data was last published", + "type": [ + "string", + "null" + ] + }, + "events": { + "items": { + "properties": { + "audience": { + "description": "kids, teens or seniors when the event is only for them", + "type": [ + "string", + "null" + ] + }, + "biz_formats": { + "items": { + "type": "string" + }, + "type": "array" + }, + "categories": { + "items": { + "type": "string" + }, + "type": "array" + }, + "city": { + "description": "Town or city within the metro", + "type": [ + "string", + "null" + ] + }, + "date": { + "description": "Local start date, YYYY-MM-DD", + "type": "string" + }, + "distance_km": { + "description": "With near: distance from the place", + "type": "number" + }, + "end": { + "type": [ + "string", + "null" + ] + }, + "first_seen": { + "type": [ + "string", + "null" + ] + }, + "free": { + "type": "boolean" + }, + "id": { + "description": "Stable 12-character id; pass it to get_event", + "type": "string" + }, + "last_fetched": { + "type": [ + "string", + "null" + ] + }, + "last_seen": { + "type": [ + "string", + "null" + ] + }, + "link": { + "description": "The original listing; keep it and credit What's Up In", + "type": [ + "string", + "null" + ] + }, + "location": { + "type": [ + "string", + "null" + ] + }, + "neighborhood": { + "type": [ + "string", + "null" + ] + }, + "performers": { + "items": { + "type": "string" + }, + "type": "array" + }, + "possibly_free": { + "type": "boolean" + }, + "posted_by_sources": { + "type": "number" + }, + "price": { + "description": "All-in price as the source states it, \"Free\", or \"See tickets\" when the source doesn't state the all-in total", + "type": [ + "string", + "null" + ] + }, + "recurring": { + "description": "weekly, biweekly or monthly when the event is one date of a series", + "type": [ + "string", + "null" + ] + }, + "region": { + "type": [ + "string", + "null" + ] + }, + "rv": { + "type": [ + "string", + "null" + ] + }, + "sectors": { + "items": { + "type": "string" + }, + "type": "array" + }, + "sold_out": { + "type": "boolean" + }, + "sources": { + "items": { + "type": "string" + }, + "type": "array" + }, + "start": { + "description": "Local start, ISO 8601, when the source gives a time", + "type": [ + "string", + "null" + ] + }, + "title": { + "type": "string" + }, + "topics": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "id", + "title", + "date" + ], + "type": "object" + }, + "type": "array" + }, + "place": { + "properties": { + "center": { + "items": { + "type": "number" + }, + "type": "array" + }, + "kind": { + "type": [ + "string", + "null" + ] + }, + "matched": { + "type": [ + "string", + "null" + ] + }, + "note": { + "type": [ + "string", + "null" + ] + }, + "radius_km": { + "type": [ + "number", + "null" + ] + }, + "unplaced_events": { + "description": "Events left out because their venue isn't mapped", + "type": "number" + } + }, + "required": [], + "type": "object" + }, + "shown": { + "description": "Events returned (at most limit)", + "type": "number" + }, + "site": { + "type": "string" + } + }, + "required": [ + "count", + "shown", + "events", + "city" + ], + "type": "object" +}
4 tool updates
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Sydney, Tokyo, Toronto, Vancouver. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. Default: all."
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Albuquerque, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Buffalo, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Shanghai, St. Louis, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
4 tool updates
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Atlanta, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Seoul, Sydney, Tokyo. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Atlanta, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Seoul, Sydney, Tokyo. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Atlanta, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Seoul, Sydney, Tokyo. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Sydney, Tokyo, Toronto, Vancouver. Default: all."
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Atlanta, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Seoul, Sydney, Tokyo. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Anchorage, Atlanta, Baltimore, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cincinnati, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Havana, Honolulu, Houston, Inland Empire, Las Vegas, London, Mexico City, Miami, Minneapolis-St. Paul, Montreal, Nashville, New Orleans, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Richmond, Rome, Salt Lake City, San Juan, Savannah, Seoul, Sydney, Tokyo, Toronto, Vancouver. list_cities has the full list."
4 tool updates
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Beijing, Berlin, Cairo, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Sydney, Tokyo. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Atlanta, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Seoul, Sydney, Tokyo. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Beijing, Berlin, Cairo, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Sydney, Tokyo. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Atlanta, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Seoul, Sydney, Tokyo. list_cities has the full list."
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Beijing, Berlin, Cairo, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Sydney, Tokyo. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Atlanta, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Seoul, Sydney, Tokyo. Default: all."
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Beijing, Berlin, Cairo, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Sydney, Tokyo. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Almaty, Atlanta, Bangkok, Beijing, Berlin, Cairo, Cancún, Cape Town, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Seoul, Sydney, Tokyo. list_cities has the full list."
4 tool updates
- Changed
get_event1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Berlin, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Tokyo. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Beijing, Berlin, Cairo, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Sydney, Tokyo. list_cities has the full list."
- Changed
list_upcoming1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Berlin, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Tokyo. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Beijing, Berlin, Cairo, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Sydney, Tokyo. list_cities has the full list."
- Changed
search_across_cities1 field changed- changed
Input schema / properties / cities / descriptionPrevious value: -"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Berlin, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Tokyo. Default: all."New value: +"Only these cities (names or slugs): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Beijing, Berlin, Cairo, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Sydney, Tokyo. Default: all."
- Changed
search_events1 field changed- changed
Input schema / properties / city / descriptionPrevious value: -"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Berlin, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Tokyo. list_cities has the full list."New value: +"Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Beijing, Berlin, Cairo, Cancún, Cleveland, Dallas-Fort Worth, DC, Denver, Detroit, Guangzhou, Honolulu, Houston, Las Vegas, London, Mexico City, Miami, Nashville, New York, Paris, Philadelphia, Phoenix, Pittsburgh, Portland, Rome, Sydney, Tokyo. list_cities has the full list."
Related MCP Connectors
Live events in 50 cities: AI/tech meetups, hackathons, conferences, concerts. Free, read-only.
Read-only search of upcoming SF Bay Area events: AI/tech, dance, music, arts, food, fitness.
Free US local event search. No signup or API key; 90-day lookahead. Paid commercial and bulk access.
Search local events in plain words: shows, pop-ups, markets, classes, with times, venues, prices.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables users to search US concerts, comedy, theater, trivia, festivals, community events, and family activities by location, date, interests, and budget, returning event details and source links without requiring an account or API key for basic search.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to browse public event listings from explore pages and fetch full detail for a single event — titles, descriptions, times, locations, host display names, and aggregate RSVP counts — across eight supported city regions. Keyless and read-only, with no guest lists, contact info, or authentication required.268 npmMIT
- AlicenseAqualityCmaintenanceProvides read-only tools for discovering, searching, and browsing events from Luma, Posh, and Partiful platforms, including event details and guest lists, with optional authenticated access to a user's Luma events.10MIT
- FlicenseNot gradedqualityBmaintenanceEnables natural-language event searches through Google Events, returning structured JSON with dates, venues, ticket links, and map details, plus support for localization, filters, and pagination.2-
Glama MCP Gateway
Add one secure layer between your agents and this server.