Gridly — AI copilot for WooCommerce

Find products

find_products

Read-only

Searches products by name, SKU, category, tag, stock, price or status, and can find products with missing data (image, description, price) or thin descriptions (max_description_words).

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": "find_products"
  }
}

Input Schema

Name	Required	Description
`sku`	No
`tag`	No
`limit`	No	How many rows to return (max 100).
`store`	No	Store address or id. Leave empty if you have only one store.
`search`	No
`status`	No
`missing`	No	Only products missing ALL of these.
`category`	No	Category name or id.
`max_price`	No
`min_price`	No
`stock_status`	No
`max_description_words`	No	Only products whose description has at most this many words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavior about finding missing data and thin descriptions, but it does not describe pagination, return shape, or other operational details beyond the annotations.

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?

The description is a single efficient sentence that front-loads the main search capability and then adds the special-case filters. Every phrase contributes to understanding what the tool can search for.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter search tool with no output schema, the description covers the main filtering capabilities and special cases reasonably well. It does not clarify optionality, default limit behavior, result shape, or how multiple filters combine, leaving some gaps for an agent to infer from the schema.

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?

With only 42% schema description coverage across 12 parameters, the description does substantial compensating work by mapping filters to name, SKU, category, tag, stock, price, and status, and by explaining special filters for missing data and max_description_words. It omits limit and store semantics, but those are already described in the schema.

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 description states a specific verb and resource: searching products by name, SKU, category, tag, stock, price, or status, plus special missing-data and thin-description searches. It clearly identifies the tool's scope, though it does not explicitly distinguish it from nearby product-related siblings such as update_products or top_products.

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 search-oriented wording, and the mention of missing data and thin descriptions gives some contextual guidance. However, there are no explicit when-to-use or when-not-to-use instructions, and no alternatives are named.

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

All Gridly — AI copilot for WooCommerce 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?