Skip to main content
Glama

List catalog products

list_products
Read-only

Products in the account's catalog with their id, price, photo count and CartViral score (0-100; 'push' products are the best candidates for clips). Use the id with generate_clips.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNoOptional text to match in the product title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed world, so the safety profile is covered. The description goes beyond them by disclosing the returned fields and explaining the 0-100 CartViral score and what 'push' products mean, which is real added context. Pagination behavior and total counts are still unmentioned, keeping it short of 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.

Conciseness5/5

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

Two compact sentences that front-load the resource and return fields, then close with the actionable next step. No filler or repetition of the tool name.

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 no output schema, the description correctly takes on the burden of explaining what comes back, and it does so field by field including the score semantics. The only shortfall is the absence of any paging or result-count framing for a list endpoint with a limit parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50% — the 'search' parameter is documented but 'limit' carries no prose in the schema, and the description says nothing about either. No filtering, paging, or cap (max 100) guidance appears in the text, so it does not compensate for the coverage gap.

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 the specific resource (the account's catalog products) and enumerates exactly what each entry carries: id, price, photo count, and CartViral score. An agent can distinguish this from import_products or generate_clips without opening a schema.

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 description implies the browse-then-generate workflow by saying 'Use the id with generate_clips,' which is a useful downstream pointer. However it never says when to prefer this over import_products (adding products) or what to do when the catalog is empty, so alternative selection is only half addressed.

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.