Ticker: Live Event Ticket Market

Get Performer Analytics

get_performer_analytics

Read-only

Returns one performer's numbers: popularity rank, average prices across its events, listings, X activity and their changes, playoff odds and prediction markets. Use it when the person asks about an artist or team rather than one event. view rank, price or social returns one row per date over range. view list returns a page of performers with no performer_id: use it to list or rank performers by category, sub-category or a number. For one event use get_event_analytics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_performer_analytics"
  }
}

Input Schema

Name	Required	Description
`page`	No	The page to read, from 1. Default 1.
`view`	No	now (default): the numbers now. rank (also a range with no view): popularity rank per date, where a higher rank is better and null means unranked, not zero. price: the day's mean get-in and median across its events, before fees and all-in. social: the day's raw X sums and each count's lowest and highest check. events: the performer's upcoming events, soonest first, at most 50. list: a page of performers with their ranks and upcoming event counts, no performer_id; include_analytics adds their numbers.
`limit`	No	Rows per page. Default 25, at most 100.
`range`	No	Lookback window over snapshot_date: 7d \| 14d \| 28d \| 90d \| all (all is bounded to ~1 year). Default 28d.
`render`	No	A rendered chart (a PNG image content block) is included ahead of the data by default. Pass render:false for a data-only (smaller) response.
`search`	No	Part of the performer's name, at least 2 characters.
`columns`	No	Specific performer_analytics columns to return (bare names). Omit for the full row.
`parking`	No	Parking events: a parking pass that is its own event (sub_category_id 75 or 'Parking' in the name). `hide` (the default) leaves them out; `only` returns parking alone; `include` returns parking beside every other event. Set `only` when the user asks for parking, `include` when they want both; leave it at `hide` otherwise.
`sort_by`	No	Sort key. Default name. A rank keeps the ranked performers; an analytics number keeps the performers that have one.
`sort_order`	No	Default asc for name, desc for every other key.
`category_id`	No	Only this category.
`performer_id`	No	The performer to look up. Ticker performer id, `pf` plus ten characters, as returned by every tool here. A marketplace id also resolves with its `vs:` prefix, and bare until 2027-09-13.
`computed_at_to`	No	Analytics computed on or before this instant.
`subcategory_id`	No	Only this sub-category.
`event_count_max`	No	At most this many upcoming events.
`event_count_min`	No	At least this many upcoming events.
`computed_at_from`	No	Analytics computed on or after this instant.
`include_analytics`	No	Add each performer's analytics numbers under analytics.
`listings_current_max`	No	At most this many listings across its events.
`listings_current_min`	No	At least this many listings across its events.

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedNov 5, 2026

addedInput schema / properties / category_id

Added value: +{
+  "description": "Only this category.",
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / computed_at_from

Added value: +{
+  "description": "Analytics computed on or after this instant.",
+  "format": "date-time",
+  "type": "string"
+}

addedInput schema / properties / computed_at_to

Added value: +{
+  "description": "Analytics computed on or before this instant.",
+  "format": "date-time",
+  "type": "string"
+}

addedInput schema / properties / event_count_max

Added value: +{
+  "description": "At most this many upcoming events.",
+  "type": "integer"
+}

addedInput schema / properties / event_count_min

Added value: +{
+  "description": "At least this many upcoming events.",
+  "type": "integer"
+}

addedInput schema / properties / include_analytics

Added value: +{
+  "description": "Add each performer's analytics numbers under analytics.",
+  "type": "boolean"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Rows per page. Default 25, at most 100.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / listings_current_max

Added value: +{
+  "description": "At most this many listings across its events.",
+  "type": "integer"
+}

addedInput schema / properties / listings_current_min

Added value: +{
+  "description": "At least this many listings across its events.",
+  "type": "integer"
+}

addedInput schema / properties / page

Added value: +{
+  "description": "The page to read, from 1. Default 1.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / parking

Added value: +{
+  "description": "Parking events: a parking pass that is its own event (sub_category_id 75 or 'Parking' in the name). `hide` (the default) leaves them out; `only` returns parking alone; `include` returns parking beside every other event. Set `only` when the user asks for parking, `include` when they want both; leave it at `hide` otherwise.",
+  "enum": [
+    "hide",
+    "include",
+    "only"
+  ],
+  "type": "string"
+}

addedInput schema / properties / search

Added value: +{
+  "description": "Part of the performer's name, at least 2 characters.",
+  "minLength": 2,
+  "type": "string"
+}

addedInput schema / properties / sort_by

Added value: +{
+  "description": "Sort key. Default name. A rank keeps the ranked performers; an analytics number keeps the performers that have one.",
+  "enum": [
+    "name",
+    "popularity_rank",
+    "lifetime_rank",
+    "computed_at",
+    "event_count",
+    "avg_median_price_current",
+    "avg_lowest_price_current",
+    "listings_current",
+    "tickets_delta_1d",
+    "tickets_delta_7d",
+    "likes_current",
+    "views_current",
+    "price_volatility_7d",
+    "price_volatility_14d"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sort_order

Added value: +{
+  "description": "Default asc for name, desc for every other key.",
+  "enum": [
+    "asc",
+    "desc"
+  ],
+  "type": "string"
+}

addedInput schema / properties / subcategory_id

Added value: +{
+  "description": "Only this sub-category.",
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / view / description

Previous value: -"now (default): the numbers now. rank (also a range with no view): popularity rank per date, where a higher rank is better and null means unranked, not zero. price: the day's mean get-in and median across its events, before fees and all-in. social: the day's raw X sums and each count's lowest and highest check. events: the performer's upcoming events, soonest first, at most 50."New value: +"now (default): the numbers now. rank (also a range with no view): popularity rank per date, where a higher rank is better and null means unranked, not zero. price: the day's mean get-in and median across its events, before fees and all-in. social: the day's raw X sums and each count's lowest and highest check. events: the performer's upcoming events, soonest first, at most 50. list: a page of performers with their ranks and upcoming event counts, no performer_id; include_analytics adds their numbers."

changedInput schema / properties / view / enum

Previous value: -[
-  "now",
-  "rank",
-  "price",
-  "social",
-  "events"
-]New value: +[
+  "now",
+  "rank",
+  "price",
+  "social",
+  "events",
+  "list"
+]

removedInput schema / required
```
Removed value: -[
-  "performer_id"
-]
```

Changed2 schema fields changedNov 4, 2026

changedInput schema / properties / view / description

Previous value: -"now (default): the numbers now. rank (also a range with no view): popularity rank per date, where a higher rank is better and null means unranked, not zero. price: the day's mean get-in and median across its events, before fees and all-in. social: the day's raw X sums and each count's lowest and highest check."New value: +"now (default): the numbers now. rank (also a range with no view): popularity rank per date, where a higher rank is better and null means unranked, not zero. price: the day's mean get-in and median across its events, before fees and all-in. social: the day's raw X sums and each count's lowest and highest check. events: the performer's upcoming events, soonest first, at most 50."

changedInput schema / properties / view / enum

Previous value: -[
-  "now",
-  "rank",
-  "price",
-  "social"
-]New value: +[
+  "now",
+  "rank",
+  "price",
+  "social",
+  "events"
+]

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / view / description

Previous value: -"now (default): the numbers now. rank, price, social: one row per date over range."New value: +"now (default): the numbers now. rank (also a range with no view): popularity rank per date, where a higher rank is better and null means unranked, not zero. price: the day's mean get-in and median across its events, before fees and all-in. social: the day's raw X sums and each count's lowest and highest check."

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / view

Added value: +{
+  "description": "now (default): the numbers now. rank, price, social: one row per date over range.",
+  "enum": [
+    "now",
+    "rank",
+    "price",
+    "social"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedOct 15, 2026

addedInput schema / properties / range

Added value: +{
+  "description": "Lookback window over snapshot_date: 7d | 14d | 28d | 90d | all (all is bounded to ~1 year). Default 28d.",
+  "enum": [
+    "7d",
+    "14d",
+    "28d",
+    "90d",
+    "all"
+  ],
+  "type": "string"
+}

addedInput schema / properties / render

Added value: +{
+  "description": "A rendered chart (a PNG image content block) is included ahead of the data by default. Pass render:false for a data-only (smaller) response.",
+  "type": "boolean"
+}

First observedOct 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is known. The description adds useful semantics — rank/view return one row per date over the range, list returns a page, null rank means unranked rather than zero — but says nothing about response size, the default rendered chart, or pagination limits beyond what the schema states.

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

Conciseness4/5

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

The return summary is front-loaded, then usage and mode routing, which is the right order for an agent deciding whether to call. It is dense but mostly earns its sentences; the repetition of view rank/price/social phrasing overlaps the schema slightly and could be trimmed.

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

Completeness3/5

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

For a 20-parameter, six-mode tool with no output schema, the description covers purpose and the main routing decision but does not explain how the many filters (category_id, sort_by, event_count_min/max, listings_current_min/max, parking) apply only to list mode, nor the now-vs-rank distinction. That gap is real, though the 100% schema coverage mitigates it.

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 description coverage is 100%, so all 20 parameters are already documented in the schema, including the view enum meanings and rank semantics. The description reinforces the view and performer_id split but adds little parameter meaning the schema does not already carry, so the 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?

The description opens with a specific verb and resource ("Returns one performer's numbers") and enumerates exactly what is in scope: popularity rank, average prices, listings, X activity with changes, playoff odds and prediction markets. It also distinguishes itself from the event-level sibling, so an agent can separate this from get_event_analytics without reading either schema.

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?

It gives explicit routing: use this when the question is about an artist or team rather than one event, and "For one event use get_event_analytics." It also explains the list mode ("no performer_id: use it to list or rank performers by category, sub-category or a number"). It stops short of covering when to pick now vs rank vs events views, leaving that to the schema.

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

All Ticker: Live Event Ticket Market 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?