Skip to main content
Glama

Search Library Images

search_user_images
Read-onlyIdempotent

Find Brand Library images by visual meaning. Search for the pictured subject. In select mode, wait for the user's choice or skip; use display mode only when the choice is delegated. Empty results mean no relevant matches were found.

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>",
      "query": "<query>"
    },
    "name": "search_user_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoUse "select" when the user should choose results, or "display" when the agent can use them directly.select
queryYesDescribe what is pictured using a short noun phrase of one to four words, such as a product or scene.
top_kNoHow many matching Library images to return at most.
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 search.

Output Schema

NameRequiredDescriptionDefault
modeYesMode the request used.
queryYesSearch query the request used.
candidatesYesMatching Brand Library images. Empty when nothing matched.
message_for_assistantNoContext, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds two useful behavioral facts beyond the annotations: the select-mode wait/skip obligation and that empty results mean no relevant match (discouraging retries). It says nothing about ranking, top_k behavior, or how results are ordered.

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?

Four short, front-loaded sentences with the core purpose first and practical caveats after; nothing is duplicated. The empty-results sentence arguably restates the obvious but earns its place by heading off retry loops.

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 an output schema present, rich annotations, and full schema coverage, the description only needs to cover call-time policy. It does so for mode handling and empty results, leaving a small gap on result ordering and how top_k interacts with select mode.

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 all five parameters including the mode enum are already documented in the schema. The description reinforces the query intent ('pictured subject') but adds no syntax, format, or default behavior beyond what the schema supplies, so the 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 concrete verb and resource: 'Find Brand Library images by visual meaning' plus the clarifying 'Search for the pictured subject.' That distinguishes it from a text search like search_docs, but it never names or contrasts the closest siblings such as list_images or search_docs explicitly.

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 provides real guidance on mode selection ('wait for the user's choice or skip' in select mode; 'use display mode only when the choice is delegated'), which is genuine when-to-use advice. However, this is parameter-level rather than tool-level routing: there is no statement of when to use this over list_images or other retrieval tools.

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