Retrieve StubHub's current search suggestions, including suggested performers, groupings, and categories, from its search interface.
List StubHub's current search suggestions. Returns StubHub's short, changing list of performers, groupings, and categories currently suggested by its search UI. The upstream endpoint is a cookie-free GET with no query parameters.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full disclosure burden. It usefully reveals that the upstream endpoint is a cookie-free GET with no query parameters, signaling a read-only, auth-free call, and that results are short and changing. It could be more explicit about the response shape, but this is solid transparency for a zero-parameter list tool.
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?
The description is two sentences with no filler: the first states purpose and content, the second adds the endpoint behavior. It is front-loaded and every sentence earns its place.
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?
For a no-input, cookie-free GET, the description covers purpose, content type, dynamic nature, and request characteristics. It is nearly complete for correct invocation; the only minor gap is the exact return format, such as whether the result is an array of strings or objects, and no output schema exists to fill that gap.
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?
There are zero parameters, so the schema already fully covers parameter semantics. The description reinforces this by explicitly stating 'no query parameters,' which is appropriate for a parameterless endpoint.
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 opens with a specific verb and resource: 'List StubHub's current search suggestions,' and further defines them as a short, changing list of performers, groupings, and categories. It makes the tool's purpose clear, though it does not explicitly contrast it with sibling tools like stubhub_search or stubhub_trending.
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?
Usage is implied: this tool is for fetching StubHub's current search-UI suggestions, with no parameters required. It does not state when not to use it or name alternatives such as stubhub_trending or stubhub_search, leaving some selection responsibility to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.