Skip to main content
Glama

Openbeautyfacts

by io.github.pipeworx-io
OverviewAdmin

Search Products

search_products
Read-onlyIdempotent

Search cosmetics and personal care products by name or keyword in Open Beauty Facts. Returns matching beauty products with barcode, name, brand, categories, and image. Useful for finding ingredients and details of shampoos, lotions, makeup, deodorants, and other personal-care items. Example: search_products("shampoo").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesProduct name or keyword (e.g., "shampoo", "lipstick")
page_sizeNoNumber of results to return (default: 20, max: 50)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "shampoo"
+  },
+  {
+    "page_size": 30,
+    "query": "lipstick"
+  }
+]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds return field details (barcode, name, brand, categories, image) but does not contradict 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?

Two sentences plus an example. Front-loaded with purpose and no unnecessary words. Every sentence adds value.

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?

Given no output schema, description explains return fields. Covers main use case but omits pagination or error details. Adequate for a simple search tool.

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%, so parameters are already documented. Description adds examples but no new semantic information beyond what schema provides. Baseline 3.

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 clearly states the verb 'search' and the resource 'cosmetics and personal care products' in 'Open Beauty Facts'. It further specifies return fields and gives examples, distinguishing it from sibling tools like get_product.

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?

The description provides context for when to use (finding ingredients/details of personal care items) but does not explicitly state when not to use or mention alternatives among siblings.

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

All Openbeautyfacts toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources