Skip to main content
Glama

Read saved image previews

list_asset_images
Read-onlyIdempotent

Read full-quality signed image links for the connected account's ready face photos or optional style references. Follow nextCursor even after an empty page. Refreshes expired links without creating images.

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_asset_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoface
limitNo
cursorNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
nextCursorYes
artifactExpiresAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description still adds meaningful behavior the annotations cannot express: the links are signed and expire but are refreshed on read, and the call never creates images.

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 short sentences, front-loaded with the resource and scope, with zero filler. Minor cost: the cursor is referred to as "nextCursor" while the schema calls it "cursor", which could momentarily blur which value to pass on the next call.

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?

An output schema exists, so return values need not be described, and the description covers role options, pagination continuation and link-refresh behavior. The only material gap is limit semantics for what is otherwise a simple three-parameter read tool.

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 0%, so the description must carry parameter meaning, and it does so only partly: it explains the face vs style-ref role distinction and names the pagination cursor (as nextCursor). The limit parameter, its maximum of 50 and defaults are left entirely to the schema.

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 pairs a specific verb ("Read") with a specific resource ("full-quality signed image links") and narrows scope to the account's ready face photos or style references. The phrase "without creating images" implicitly separates it from the create/import/generation siblings, though no sibling is named directly.

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?

It gives one concrete operational rule — follow the cursor even after an empty page — which is genuinely useful for correct invocation. However, it offers no explicit when-to-use guidance against alternatives such as list_assets, and no exclusions or prerequisites are stated.

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