MONO Social

list_products

Read-onlyIdempotent

List products in this site's store (Wix Stores). Returns name, price, stock status, and product type.

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

Name	Required	Description	Default
`q`	No	Optional search term matched against product name.
`limit`	No	Max products to return (default 20, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 21, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent, non-destructive closed-world read, so the description's main added value is enumerating return fields (name, price, stock status, product type), which matters because there is no output schema. It does not mention that results are capped by page size or whether the list is ordered in any way.

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: scope first, return shape second. Every clause carries information and nothing is padded.

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?

For a zero-required-parameter read tool the description is nearly sufficient: it covers scope and return shape, and the schema fully documents both inputs. A note on paging behavior or result ordering would close the last gap, especially with no output schema.

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 coverage is 100%, with both q and limit fully documented including the default 20 and max 100, so the description adds nothing beyond the schema. Baseline 3 applies when the schema carries parameter semantics.

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?

States a specific verb (List) and resource (products) with explicit scoping to 'this site's store (Wix Stores)' plus a summary of the returned fields, so an agent knows exactly what it gets. No sibling in the tool set offers products, so differentiation is implicit rather than stated.

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?

Usage is implied by the name and the 'in this site's store' scoping, but there is no explicit when-to-use guidance, no mention of prerequisites (e.g., store must exist on the site), and no named alternatives such as list_categories for browsing taxonomy instead.

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

All MONO Social 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?