Skip to main content
Glama
Sign In

Shootika

by com.shootika
OverviewDiscussionsAdmin

List products

list_products
Read-only

Lists the store's products, newest first, 24 per page, each with its id, title, family, garment_category, accessory_kind, shoot_routes (on_model, placement, both or none: the shoots it can have) and photos (the source images shoots start from). Use it to find a product id. Pass external_id to look one up by the store's own id. The result carries page, page_size and total; when more pages exist, call again with page + 1.

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
pageNoPage number, starting at 1. Omit for the first page.
external_idNoReturn only the product whose external_id (the store's own id) matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Well beyond the readOnly/non-destructive annotations, it discloses sort order, page size, the returned field set, and the pagination protocol ('when more pages exist, call again with page + 1'). It does not cover what happens when external_id matches nothing or how pagination interacts with the external_id filter, which keeps it off 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?

Front-loaded with what is listed, then pagination, then lookup mode — the order in which an agent needs the facts. Three dense sentences with no filler, despite the long field enumeration.

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?

There is no output schema, but the description compensates by enumerating the returned fields and the page/page_size/total envelope, plus the continuation rule. An agent has everything needed to call it and page through results correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds operational meaning: external_id is framed as a single-record lookup path and page as a continuation cursor tied to the returned page/page_size/total envelope. That is more than the schema's field-level notes convey.

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 plus distinguishing scope: 'Lists the store's products, newest first, 24 per page'. It follows with the exact fields returned, so an agent can tell this apart from get_product (single record) 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 Guidelines4/5

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

Gives explicit intent ('Use it to find a product id') and the condition for the alternate mode ('Pass external_id to look one up by the store's own id'). It does not name a sibling alternative such as get_product when the id is already known, leaving one routing decision to inference.

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

All Shootika 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