Skip to main content
Glama

tito

by io.usefulapi
OverviewDiscussionsAdmin

List tickets (attendees)

tito_list_tickets
Read-only

List an event's tickets — one per attendee — newest first, with name, email, company, reference, release, price paid and state. Filter by free text (name, email, phone, reference, company, tag), state, type, release, activity, and created/updated time. Void tickets are excluded unless states includes 'void'. Tito: GET /:account/:event/tickets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search: email, name, phone, slug, reference, company or tag.
pageNoPage number (page[number]), from 1.
sortNoSort attribute (search[sort]). Default created_at, newest first.
viewNoResponse view. Lists default to 'short'; 'extended' includes associated records but can be slow and large.
typesNomanual = added by an organiser, standard = ordered by a customer (search[types][]).
statesNoOnly these states (search[states][]). 'archived' also includes tickets of archived releases.
directionNoSort direction (search[direction]).
page_sizeNoResults per page (page[size]), 1-1000. Tito's default is 100.
event_slugYesThe event slug (the second part of https://ti.to/<account>/<event>), e.g. 2026.
account_slugNoThe account slug (the first part of https://ti.to/<account>/<event>). Optional if TITO_ACCOUNT is set; tito_whoami lists the accounts this token can reach.
activity_idsNoOnly tickets attached to these activity ids (search[activity_ids][]).
created_afterNoOnly tickets created after this time (search[created_at][gt]), e.g. 2026-01-01T09:00:00+UTC. Without the +UTC suffix Tito uses the event's own time zone.
release_slugsNoOnly tickets of these releases, by release slug (search[release_ids][]).
updated_afterNoOnly tickets updated after this time (search[updated_at][gt]), e.g. 2026-01-01T09:00:00+UTC. Without the +UTC suffix Tito uses the event's own time zone.
created_beforeNoOnly tickets created before this time (search[created_at][lt]), e.g. 2026-01-01T09:00:00+UTC. Without the +UTC suffix Tito uses the event's own time zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint=true already declaring a safe read, the description adds genuine behavioral context: the default exclusion of void tickets, the newest-first default ordering, and the returned field set. What it doesn't cover (pagination semantics under 'extended', rate limits) is partly handled by schema notes on view/page_size.

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?

Three sentences, front-loaded with the resource and cardinality, then filters, then the one non-obvious default. Slightly dense in the middle (a long comma list that mirrors the schema), but nothing is wasted.

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

Completeness4/5

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

For a 15-parameter read tool with no output schema, the description usefully enumerates returned fields and the void-exclusion default. It leaves the required vs optional distinction and account_slug fallback to the schema, which documents them, so the result is adequate though not exhaustive.

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 the schema already documents all 15 parameters with syntax and Tito-specific keys. The description echoes the filter categories and the void-exclusion interaction with 'states' — mildly useful but largely redundant against the schema baseline of 3.

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+resource (list an event's tickets), the cardinality (one per attendee), default ordering (newest first), and enumerates the fields returned. An agent can distinguish this from tito_get_ticket (single) and tito_list_registrations (different resource) without opening the 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 names the filterable dimensions (free text, state, type, release, activity, created/updated time) and gives a concrete default behavior — void tickets are excluded unless 'void' appears in states — which is a real when/when-not condition. It stops short of naming sibling alternatives for adjacent tasks (e.g., fetching one ticket).

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

All tito toolsInspect
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