Skip to main content
Glama

Tito MCP by usefulapi

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. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses the default sort ('newest first'), the fields returned, and the non-obvious default exclusion of void tickets — none of which are in the annotations. It omits pagination/auth behavior, but the SQL-shaped void rule is genuinely useful context.

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 dense sentences, front-loaded with the resource and scope, then filtering, then the void rule, then the endpoint. Every sentence earns its place; the long filter list is compact but slightly run-on.

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-only list tool with no output schema, the description covers what is returned, the default ordering, and the default void exclusion. Defaults like page_size (100) and view (short) live in the schema, so their absence from the description is acceptable.

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

Parameters4/5

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 lifts this above baseline by surfacing one cross-parameter rule (void excluded unless 'states' includes 'void') and summarizing the filter families the parameters cover.

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 ('List an event's tickets — one per attendee') plus the scope and the fields returned, which cleanly separates it from the singular siblings tito_get_ticket and tito_list_registrations.

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 concrete filtering context (free text, state, type, release, activity, time) and a real selection rule — void tickets are excluded unless 'states' includes 'void'. It stops short of naming an alternative tool or an explicit when-not condition.

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

All Tito MCP by usefulapi 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