Skip to main content
Glama
Sign In

SnapWidget

by com.snapwidget
OverviewDiscussionsAdmin

Search Products

search_products
Read-only

Finds products in the product feeds that the user added on the Shoppable page, by words of the product name or link: url, name, image, price, currency and available (false: sold out). At most 20. Use a product's url and name as the url and description of a tag in set_product_tags. Paid plans.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWords of the product name or link, for example "linen shirt".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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=false, so safety is covered. The description adds real value beyond that by disclosing the result cap ('At most 20'), the returned fields, the sold-out semantics of 'available', and the paid-plan requirement. However, it says nothing about matching behavior (fuzzy vs exact), empty results, or pagination past 20.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

It is front-loaded with purpose first and contains little waste, but the return-field list and the set_product_tags pointer are packed into the same run-on sentence, making the field enumeration slightly hard to parse.

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 one-parameter search with no output schema, the description does the necessary work: source scope, result cap, returned fields, and the plan gate. Only the matching semantics and behavior on zero results are left implicit.

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 parameter already carries the meaning ('Words of the product name or link, for example "linen shirt"'). The prose only restates that query matches name or link words, adding no syntax, matching, or escaping detail beyond the schema.

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?

The description uses a specific verb and resource ('Finds products in the product feeds') and scopes the source ('that the user added on the Shoppable page') plus the matching basis ('by words of the product name or link'). It even enumerates the returned fields, so an agent can tell exactly what this tool does versus mutation siblings like set_product_tags.

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?

It gives clear context for use and a follow-on workflow ('Use a product's url and name as the url and description of a tag in set_product_tags'), plus a prerequisite ('Paid plans.'). It stops short of naming when NOT to use it or what alternative to pick if the product is absent.

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

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