agentee

List collections

list_collections

Read-onlyIdempotent

List active curated collections — themed landing pages on allover.art, trending first — with title, slug and url. Use it when the human wants ideas or a themed page to browse; send them the url. Collections are not a search filter: to find products in a theme, call search_products with theme or query. limit caps the list (default 50, max 100). Read-only.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Max collections to return (default 50, max 100).

Output Schema

Name	Required	Description	Default
`collections`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 16, 2026

addedInput schema / properties / limit / description

Added value: +"Max collections to return (default 50, max 100)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "collections": {
+      "items": {
+        "properties": {
+          "slug": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "description": "Collection landing page.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedJul 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description nonetheless adds the ordering guarantee ("trending first") and the fact that only "active" collections appear, which the annotations do not convey. The trailing "Read-only" largely restates the annotation rather than adding new behavior, and pagination/truncation behavior beyond the cap is not described.

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?

Four compact sentences, front-loaded with the resource definition, then intended use, then the exclusion routing, then the parameter note. No padding; even the short tail sentences carry routing or constraint 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?

Output schema exists so return values need not be explained, yet the description still names the key fields. With one optional parameter fully documented and annotations covering safety, nothing an agent needs to invoke this correctly 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% and the single `limit` parameter is already documented as "default 50, max 100" in the schema; the description repeats that verbatim without adding format or semantics beyond it. With the schema doing the work, this sits at the baseline.

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

Purpose5/5

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

States a specific verb and resource ("List active curated collections") and immediately defines what a collection is ("themed landing pages on allover.art") plus the ordering ("trending first") and returned fields (title, slug, url). An agent can distinguish this from search_products or get_product without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ("when the human wants ideas or a themed page to browse; send them the url") and an explicit negative case naming the alternative tool ("Collections are not a search filter: to find products in a theme, call search_products with theme or query"). Both when-to-use and when-not-to-use are covered with the sibling named.

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

All agentee tools Inspect

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

Need Help?