Skip to main content
Glama

List Library

list_library
Read-onlyIdempotent

List the files in a Brand Library, most recently added first. Each item has a media ID, a stable link, and a description when one exists.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brand_session_id": "<brand_session_id>"
    },
    "name": "list_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoMedia family to include in the Brand Library results. Omit to include every family.
limitNoNumber of matching items to include on this page. Omit to return 20 items.
cursorNoPass next_cursor from the previous result to get the next page.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
brand_session_idYesBrand session ID from list_brands for the brand whose Library to use.

Output Schema

NameRequiredDescriptionDefault
itemsYesLibrary files, most recently added first.
has_moreYesWhether more results follow this page.
next_cursorYesPass as cursor to get the next page. Null when no more results follow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral value: the sort order and the shape of each item (media ID, stable link, optional description), which the annotations do not convey.

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 short sentences, zero filler, with the ordering constraint and item shape front-loaded. Nothing could be removed without losing information.

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

Completeness4/5

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

With a full output schema, rich annotations and 100% param coverage, the description only needs to establish scope and behavior, which it does. The one gap is not relating this listing to the sibling list_images/list_videos/list_audio tools, which is the most likely source of mis-selection.

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 type, limit, cursor, llm_model and brand_session_id are all documented in the schema. The description adds no filtering, paging or default-count semantics of its own, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb plus resource ('List the files in a Brand Library') and adds the ordering rule ('most recently added first'), which distinguishes it from generic siblings like list_images or list_audio by scope. It stops short of naming those siblings as alternatives, so it is clear but not maximally differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The Brand Library scope implies when to use it, but there is no explicit when-to-use or when-not guidance and no mention of how it relates to list_images/list_videos/list_audio, which return similar media types. The prerequisite (brand_session_id from list_brands) lives in the schema, not the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources