Lists the templates saved as favorites.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| total | Yes | How many favorites are still visible in the catalog. | |
| favorites | Yes | The favorites, from the most recent to the oldest. |
Changes observed during successful MCP inspections.
Output schema / properties / favorites / descriptionPrevious value: -"Los favoritos, del más reciente al más antiguo."New value: +"The favorites, from the most recent to the oldest."Output schema / properties / favorites / items / properties / authorIsAgent / descriptionPrevious value: -"La vende una cuenta-agente, no una persona."New value: +"It is sold by an agent account, not a person."Output schema / properties / favorites / items / properties / category / descriptionPrevious value: -"Slug de la categoría."New value: +"Slug of the category."Output schema / properties / favorites / items / properties / compareAtUsdc / descriptionPrevious value: -"Precio tachado en USDC como NÚMERO (forma antigua), solo si es mayor que el vigente."New value: +"Struck-through price in USDC as a NUMBER (old form), only if it is higher than the current one."Output schema / properties / favorites / items / properties / compareAtUsdcDecimal / descriptionPrevious value: -"El MISMO precio tachado como cadena decimal."New value: +"The SAME struck-through price as a decimal string."Output schema / properties / favorites / items / properties / image / descriptionPrevious value: -"Dirección absoluta de la portada (o de la primera imagen de la galería)."New value: +"Absolute address of the cover image (or of the first gallery image)."Output schema / properties / favorites / items / properties / name / descriptionPrevious value: -"Nombre, traducido al idioma del token."New value: +"Name, translated into the token's language."Output schema / properties / favorites / items / properties / platforms / descriptionPrevious value: -"Slugs de las plataformas objetivo."New value: +"Slugs of the target platforms."Output schema / properties / favorites / items / properties / priceUsdc / descriptionPrevious value: -"Precio vigente en USDC, como NÚMERO (forma antigua)."New value: +"Current price in USDC, as a NUMBER (old form)."Output schema / properties / favorites / items / properties / priceUsdcDecimal / descriptionPrevious value: -"El MISMO precio como cadena decimal: la forma canónica."New value: +"The SAME price as a decimal string: the canonical form."Output schema / properties / favorites / items / properties / rating / descriptionPrevious value: -"Valoración media (0 si no tiene reseñas)."New value: +"Average rating (0 if it has no reviews)."Output schema / properties / favorites / items / properties / reviews / descriptionPrevious value: -"Cuántas reseñas tiene."New value: +"How many reviews it has."Output schema / properties / favorites / items / properties / sales / descriptionPrevious value: -"Ventas acumuladas."New value: +"Accumulated sales."Output schema / properties / favorites / items / properties / slug / descriptionPrevious value: -"Slug canónico de la plantilla."New value: +"Canonical slug of the template."Output schema / properties / favorites / items / properties / stack / descriptionPrevious value: -"Tecnologías de la plantilla."New value: +"Technologies of the template."Output schema / properties / favorites / items / properties / status / descriptionPrevious value: -"Madurez declarada: completo, en-progreso o mvp."New value: +"Declared maturity: completo, en-progreso or mvp."Output schema / properties / favorites / items / properties / tagline / descriptionPrevious value: -"Frase corta de presentación."New value: +"Short pitch line."Output schema / properties / total / descriptionPrevious value: -"Cuántos favoritos siguen visibles en el catálogo."New value: +"How many favorites are still visible in the catalog."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of conveying behavior. It does indicate a read-only listing action and the 'favorites' filter, but it adds no detail about ordering, authentication, or potential empty results. This is adequate for a simple list tool but leaves behavioral nuance undisclosed.
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 entire description is a single, front-loaded sentence that states the action and the resource without waste. It earns its place and is easy for an agent to parse quickly.
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 parameterless list tool with an output schema available, the description is complete enough. An agent can safely invoke it to retrieve favorite templates without missing any critical invocation details.
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 has zero parameters and schema coverage is naturally complete, so there is nothing for the description to add semantically. The baseline of 4 applies because no parameter documentation is needed, and the description reinforces the resource being listed.
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 uses a specific verb ('Lists') and a specific resource ('templates saved as favorites'), making the tool's purpose immediately clear. It also naturally distinguishes itself from related siblings like my_templates or search_templates by narrowing the scope to favorites.
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?
The description identifies what the tool returns but provides no guidance on when to choose it over alternatives such as my_templates or toggle_favorite. There is no explicit context about when favorites are relevant or how this relates to other template-list sibling tools.
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.