export_guest_list_csvExport a live event's guest list as a downloadable CSV (name, email, phone, category, ticket class, plus-ones, checked-in, note) and return a download link. Optional category filter. Requires event_id; you must be a host. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | ||
| event_id | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare `readOnlyHint=true`, `idempotentHint=true`, `destructiveHint=false`. The description adds that it returns a download link and enumerates the data fields, providing concrete output behavior beyond the generic hints.
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 action and result, no wasted words. Every sentence adds value.
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 no output schema, the description covers the return format (download link, field list), filter option, and access requirement. Complete for the tool's purpose.
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 0%. The description mentions the optional `category` filter (adding meaning) but only notes that `event_id` is required without further detail. It partially compensates for missing schema descriptions.
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 clearly states the tool exports a live event's guest list as a downloadable CSV, listing specific fields and stating it returns a download link. This distinguishes it from sibling tools like `list_guests` or `export_form_responses_csv`.
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 requires `event_id` and states the user must be a host, plus it is read-only. It indicates an optional category filter but does not directly contrast with alternatives like `list_guests` for JSON output.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.