list_presetsFetch all Globestudio look presets with IDs, names, blurbs, vibe tags, thumbnails, and embed URLs. Use this first to answer user questions about available looks.
List every Globestudio look preset with its id, name, blurb, vibe tags, thumbnail URL and embed URL. Call this first when the user asks about available looks.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered structurally. The description adds behavior the annotations do not: it returns EVERY preset unfiltered, implying no input-driven narrowing, and it enumerates the response fields, which is valuable given there is no output schema.
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, no filler, and the action plus returned payload is front-loaded before the routing hint. Every clause 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?
With no output schema, the description compensates well by listing the return fields, and the annotations cover safety. The only real gap is that the boundary with find_presets is never stated, which matters since both could appear to answer 'show me looks'.
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?
The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to document. Nothing in the description misrepresents the parameterless contract.
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?
States a specific verb (List) and resource (Globestudio look presets) and enumerates exactly which fields come back (id, name, blurb, vibe tags, thumbnail URL, embed URL). The word 'every' plus the field list distinguishes it from the narrower find_presets sibling.
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?
'Call this first when the user asks about available looks' gives an explicit trigger condition, which is strong usage guidance. It stops short of naming find_presets as the alternative for filtered/searched lookups, so the when-not case is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.