Skip to main content
Glama
Sign In
Hermoso

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List library

list_library
Read-onlyIdempotent

Browse the Library to view Studio-generated images and videos, newest first, with served URLs and asset IDs for downloads or ad inserts. Free, read-only.

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 id (L0, L1…, which plan_ad and render_ad inserts take), kind, model, and age. Free, read-only.

Input 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.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety is covered; the description then adds genuinely new behavior: newest-first ordering, 'Free' (no credit cost), the shape of the return (served URLs, id, kind, model, age), and that it mirrors the web app's Library.

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?

Dense but front-loaded: identity and scope first, then return shape, then the id-consumer relationship and cost. Every clause carries information an agent needs, with no filler or repetition of the schema.

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?

There is no output schema, so the description must carry the return contract — and it does, naming served URLs, asset ids (L0, L1…), kind, model, and age, plus how those ids are consumed downstream. Combined with the covered annotations, nothing needed to call it correctly 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 `kind` and `limit` (defaults, enum, max 60) are already fully documented in the schema. The description only alludes to kind by mentioning image/video assets and never mentions limit, so it adds no meaningful semantics beyond the schema — baseline 3.

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?

States a specific verb (Browse/List) and resource (this workspace's Library) with precise scope: every image/video generated in the Studio, newest first. This cleanly separates it from lookalike list tools such as list_drive_files, list_swipefile, and list_onedrive_files, which cover different content sources.

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?

Gives clear usage context: browse generated assets, and hand served URLs to fetch_asset for a download link; ids feed plan_ad/render_ad `inserts`. It does not explicitly state when to prefer a sibling (e.g., list_drive_files for Drive-hosted files) or any exclusions, so it stops short of full routing guidance.

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