Skip to main content
Glama

List saved items

list_saved_items
Read-onlyIdempotent

Lists the account's active saved characters, references, voice recordings, moodboards and brand kits, newest first. Reusable paths are in each item's assets[].file_path; temporary signed URLs support preview/download. Read-only; pass next_cursor as cursor for the next page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_saved_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly return saved items of this type.
limitNoMaximum number of saved items to return. Defaults to 20.
cursorNoOpaque pagination cursor from the previous response's next_cursor.

Output Schema

NameRequiredDescriptionDefault
itemsYes
next_cursorYesCursor for the next page, or null when there are no more saved items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. Beyond that, the description adds genuinely useful behavior: only *active* items are returned, ordering is newest-first, and it explains the crucial distinction between permanent assets[].file_path values and temporary signed URLs used for preview/download. Minor redundancy in repeating "Read-only" keeps it from a 5.

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

Conciseness4/5

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

Three dense sentences, front-loaded with the core purpose and scope, with pagination guidance last. There is mild waste in the "Read-only" clause echoing readOnlyHint, but nothing else could be cut without losing information.

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?

With only three optional, fully documented parameters, an output schema in place, and annotations covering safety, this description fills the remaining gaps: which items qualify (active), their order, pagination mechanics, and the file_path vs. signed-URL distinction that determines how a caller retrieves each asset.

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%, with the type enum, limit bounds/default and cursor semantics all documented in the schema itself. The description only reinforces the cursor→next_cursor round trip, which the schema already states, and adds no filtering or format detail beyond it. 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 first sentence gives a specific verb ("Lists"), a scoped resource ("the account's active saved items") and enumerates the five item types, plus ordering ("newest first"). An agent knows exactly what this returns, though it does not name a sibling it might be confused with (e.g. voices_list for voice items).

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?

Usage is implied: fetch saved assets, filter by type, page with next_cursor. It states read-only and how to paginate, but gives no when-not conditions, no prerequisites, and no routing to an alternative tool for retrieving a single item or a different asset class.

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.