TicketSea

Get event details

get_event

Read-onlyIdempotent

Use this when you have an event's slug from a search result and need that event's current details: date, local time, venue, sale state, cancellation and any published price range. Returns the newest available snapshot; older details are returned explicitly marked stale.

Input Schema

Name	Required	Description	Default
`slug`	Yes	Exact event slug from a search result; not an artist or venue slug.

Output Schema

Name	Required	Description	Default
`url`	Yes
`city`	Yes
`date`	Yes
`name`	Yes
`slug`	Yes
`stale`	Yes
`venue`	Yes
`notice`	Yes
`onSale`	Yes
`region`	Yes
`status`	Yes
`country`	Yes
`pricing`	No
`tickets`	No
`dateTime`	Yes
`timezone`	Yes
`localTime`	Yes
`publicSaleState`	Yes
`listingUpdatedAt`	Yes
`inventoryVerified`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 22, 2026

removedOutput schema / properties / date / description

Removed value: -"Venue-local date; may be blank if unknown."

removedOutput schema / properties / dateTime / description

Removed value: -"Provider absolute start timestamp when supplied."

removedOutput schema / properties / listingUpdatedAt / description

Removed value: -"Original listing retrieval timestamp; not a stock check."

removedOutput schema / properties / localTime / description

Removed value: -"Venue-local time; may be blank if unknown."

removedOutput schema / properties / pricing / description

Removed value: -"Informational published ranges, not current available offers. Prices may change moment to moment and are not guaranteed. Fees and taxes may be additional. When ranges is empty, omit the price line. Never combine primary/resale sellers or currencies."

removedOutput schema / properties / pricing / properties / inventoryVerified / const
```
Removed value: -false
```

removedOutput schema / properties / pricing / properties / ranges / items / properties

Removed value: -{
-  "checkedAt": {
-    "type": "string"
-  },
-  "currency": {
-    "type": "string"
-  },
-  "feeInclusion": {
-    "const": "unknown",
-    "type": "string"
-  },
-  "label": {
-    "type": "string"
-  },
-  "maxMinor": {
-    "minimum": 1,
-    "type": "integer"
-  },
-  "minMinor": {
-    "minimum": 1,
-    "type": "integer"
-  },
-  "minorUnit": {
-    "maximum": 3,
-    "minimum": 0,
-    "type": "integer"
-  },
-  "provider": {
-    "type": "string"
-  },
-  "sourceType": {
-    "type": "string"
-  },
-  "validUntil": {
-    "description": "Expiry in Unix milliseconds. Discard at this time even if cached.",
-    "type": "integer"
-  }
-}

removedOutput schema / properties / pricing / properties / ranges / items / required

Removed value: -[
-  "provider",
-  "sourceType",
-  "currency",
-  "minMinor",
-  "maxMinor",
-  "minorUnit",
-  "checkedAt",
-  "validUntil",
-  "label",
-  "feeInclusion"
-]

removedOutput schema / properties / publicSaleState / description

Removed value: -"Schedule state, not inventory. registration means restricted registration access, not an open general sale."

removedOutput schema / properties / tickets / description

Removed value: -"The first exact-event seller link for this performance, present only for a fresh, upcoming listing with a known seller page. The link opens the seller's page for this event through ticketsea.com/go/. It is not an availability check, and the event can have other sellers."

removedOutput schema / properties / tickets / properties / affiliate / description
```
Removed value: -"TicketSea may earn a commission from this seller."
```
removedOutput schema / properties / tickets / properties / type / description
```
Removed value: -"primary or resale."
```
removedOutput schema / properties / tickets / properties / url / format
```
Removed value: -"uri"
```

removedOutput schema / properties / timezone / description

Removed value: -"Provider timezone; may be blank if unknown. Do not invent one."

removedOutput schema / properties / url / format
```
Removed value: -"uri"
```

Changed2 schema fields changedOct 12, 2026

changedInput schema / properties / slug / description

Previous value: -"Exact event slug returned by search_events; not an artist or venue slug."New value: +"Exact event slug from a search result; not an artist or venue slug."

changedOutput schema / properties / tickets / description

Previous value: -"The first exact-event seller link for this performance, present only for a fresh, upcoming listing with a known seller page. The link opens the seller's page for this event through ticketsea.com/go/. It is not an availability check; get_ticket_links lists every seller."New value: +"The first exact-event seller link for this performance, present only for a fresh, upcoming listing with a known seller page. The link opens the seller's page for this event through ticketsea.com/go/. It is not an availability check, and the event can have other sellers."

First observedOct 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for adding freshness semantics not present in structured data: it returns the newest snapshot and flags older details as stale. That staleness signal is genuinely useful for an agent deciding whether to trust the data. Return field details are somewhat redundant with the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the trigger condition, then the payload and the freshness caveat. Every clause contributes something: usage condition, returned fields, staleness behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description doesn't need to specify return structure — and it correctly stops at naming the key fields. Combined with the freshness/staleness note and the slug provenance, an agent has everything needed to call this correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the slug parameter already documents format and the 'not artist/venue' restriction. The description only restates that the slug comes from a search result, adding a small amount of provenance context rather than new syntax or format meaning. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('get that event's current details') and enumerates the returned facets (date, local time, venue, sale state, cancellation, price range). This clearly distinguishes it from sibling lookups like get_ticket_prices, get_ticket_links, and search_events.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear triggering condition: 'when you have an event's slug from a search result.' That implicitly routes the agent to run search_events first when no slug exists, and the schema reinforces 'not an artist or venue slug.' However, no sibling is named explicitly and no when-not-to-use case is stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TicketSea tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?