Skip to main content
Glama
Sign In

Webanto

by com.webanto
OverviewDiscussionsAdmin

List managed image metadata

webanto_list_assets
Read-onlyIdempotent

Read a bounded page of existing product or content-entry image metadata, with exact-version source references and native review links. Metadata approval covers copy, not image reuse. This is not an uploaded-asset library, generated artwork, byte verification or permission to attach/reuse images externally. No private source URLs, provider errors, generation, publication or credit cost.

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": {
      "parent": "<parent>"
    },
    "name": "webanto_list_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentYesExact organization-owned product or content entry whose managed image metadata is requested.
after_idNoLast image identifier from the previous page, in ascending identifier order.
page_sizeNoMaximum metadata records, at most 20.

Output Schema

NameRequiredDescriptionDefault

No arguments

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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: bounded page size, exact-version source references, native review links, no private source URLs or provider errors surfaced, and no credit cost — all material for an agent deciding whether to call it.

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?

The scope sentence is front-loaded and the exclusions are compact. The final clause ('No private source URLs, provider errors, generation, publication or credit cost') is telegraphic and slightly unclear as a return-value claim, but the definition carries no padding.

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 shape needs no explanation, and all three parameters are fully schema-described. The description supplies the safety and scope framing an agent needs for a paginated read; only an explicit alternative-tool pointer 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 parent variants, after_id, and page_size are already documented in the schema. The description restates 'bounded page' but adds no cursor semantics, ordering, or identifier-format detail beyond what the schema provides; 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 (read a bounded page), a precise resource (product or content-entry image metadata), and scope (pagination plus source references and review links). It also carves out what the tool is not (uploaded-asset library, generated artwork), which separates it from get_asset and generation tools, though it never names a sibling 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?

The usage context is implied: enumerate image metadata for a parent product or content entry. Exclusions ('not an uploaded-asset library', 'not permission to attach/reuse images') clarify boundaries, but there is no positive 'use this tool when you need X, otherwise use get_asset' routing statement.

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

All Webanto toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources