Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List library

list_library
Read-onlyIdempotent

Browse images and videos generated in this workspace's Studio library, newest first. Returned assets include served URLs for direct opening or download-link retrieval, plus kind, model, and age; filter by image or video.

Instructions

Browse this workspace's Library — every image/video generated in the Studio, newest first (the same Library the web app shows). Returns served URLs you can open directly or hand to fetch_asset for a download link, plus each asset's kind, model, and age. Free, read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNofilter by asset kind (default 'all')
limitNomax assets to return (default 20, max 60)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "assets": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "ageHours": {
-            "type": "number"
-          },
-          "kind": {
-            "type": "string"
-          },
-          "model": {
-            "type": "string"
-          },
-          "url": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "url"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Addedv0.1.15

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, and non-destructive. The description adds genuinely useful behavioral context: the result set is newest-first, matches the web app's Library, returns served URLs, and includes each asset's kind, model, and age. It also notes the operation is free, which is useful cost-related transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences, with the most important scope information ('workspace Library', 'newest first') front-loaded. Returns, downstream usage, and cost/read-only status are conveyed with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description clearly explains what the tool returns: served URLs, asset kind, model, and age. It also covers ordering, scope, and how to connect to fetch_asset. For a simple list operation with well-covered parameters and rich annotations, nothing critical is missing.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters (kind and limit) are already documented in the input schema. The description adds light semantic context by mentioning images/videos and asset kinds, but it does not meaningfully extend beyond the schema. Baseline 3 is appropriate.

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?

The description uses a specific verb ('Browse') and identifies the exact resource: this workspace's Library, containing every image/video generated in the Studio, newest first. It also clarifies the tool's scope with 'the same Library the web app shows,' making it easy to distinguish from generic list_* siblings.

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?

The description gives clear context for when to use the tool: browsing generated assets in the workspace Library. It also points the agent to a concrete follow-up path by saying served URLs can be handed to fetch_asset for a download link. It does not explicitly enumerate when not to use it versus other listing tools, but the context is strong enough.

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

Deploy Server

Other Tools