Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

woo_products

Read-onlyIdempotent

Retrieve WooCommerce products from a store by listing them with filters like status or category, or fetch a single product by ID using your store URL and API credentials.

Instructions

List or get WooCommerce products.

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": {
      "store_url": "<store_url>",
      "consumer_key": "<consumer_key>",
      "consumer_secret": "<consumer_secret>"
    },
    "name": "woo_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoProduct ID for action='get'
pageNo
orderNo
actionNolist or get (default: list)
searchNo
statusNopublish, draft, pending, private
orderbyNo
categoryNo
per_pageNo
store_urlYesWooCommerce store URL (e.g. https://mystore.com)
consumer_keyYesWooCommerce consumer key (ck_...)
consumer_secretYesWooCommerce consumer secret (cs_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds nothing beyond restating the resource and verbs—no mention of pagination, filtering behavior, authentication requirements, or response shape.

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

Conciseness3/5

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

The single sentence is concise and front-loaded, but it is underspecified rather than efficient. Brevity here comes at the cost of necessary operational detail, so it does not fully earn its place.

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

Completeness2/5

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

With 12 parameters, 50% schema coverage, no output schema, and no annotations explaining operational behavior, the description leaves too much unspecified. It should at least clarify the list/get duality, common filters, and pagination expectations.

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%, and the description provides no parameter information at all. Critical filters like search, category, orderby, per_page, page, and order are undocumented in both schema and description, so an agent cannot infer their 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?

The description provides a clear verb ('List or get') and resource ('WooCommerce products'), so an agent knows exactly what the tool operates on. However, it does not differentiate this from sibling tools like woo_orders or woo_customers, leaving ambiguity about scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description only says 'List or get' and gives no guidance on when to choose list versus get, when to use it over related tools, or what prerequisites exist. The action parameter is documented in the schema, but the description adds no selection criteria.

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

Deploy Server

Other Tools