Boring API

Validate a product feed

merchant_validate

Read-onlyIdempotent

Checks a product feed or catalog export for Google Merchant Center, Shopify or Meta (Facebook/Instagram) before upload. Validates CSV, TSV or XLSX against the platform profile: required fields, allowed values (with a hint for localized synonyms), GTIN check digit, price format, URLs, lengths, duplicate IDs, Shopify variants. Every issue names row, column, rule code and a fix hint; nothing is changed. The feed can be passed as upload, URL or CSV text.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`file`	No	The feed. A file uploaded in ChatGPT (object with download_url and file_id).
`options`	No	Optional ValidateOptions, e.g. {"sheet": "Feed", "column_overrides": {"gtin": "EAN code"}, "max_issues": 500}. Schema: /v1/schemas/merchant-validate-options.
`profile`	No	Target platform: google_merchant, shopify_products_csv or meta_catalog.	google_merchant
`file_url`	No	The feed. Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB.
`filename`	No	Original filename with extension (e.g. prices.xlsx); used to detect the format.
`file_path`	No	Local file path; only allowed when the server runs locally over stdio.
`file_text`	No	The feed. The table as CSV or TSV text, header row first (e.g. 'SKU;Price;Currency\nA1;12.50;EUR').
`file_base64`	No	The feed. File content as Base64 (standard alphabet). Max 20 MiB decoded.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 6, 2026

changedInput schema / properties / file / description

Previous value: -"The feed. A file the user uploaded in ChatGPT (filled in by ChatGPT; other clients use the URL)."New value: +"The feed. A file uploaded in ChatGPT (object with download_url and file_id)."

changedInput schema / properties / file_base64 / description

Previous value: -"The feed. File content as Base64 (standard alphabet). Max 20 MiB decoded; prefer a URL or upload."New value: +"The feed. File content as Base64 (standard alphabet). Max 20 MiB decoded."

changedInput schema / properties / file_text / description

Previous value: -"The feed. The table as CSV or TSV text, header row first (e.g. 'SKU;Price;Currency\\nA1;12.50;EUR'). Use this when you can read the user's spreadsheet but cannot pass the file itself."New value: +"The feed. The table as CSV or TSV text, header row first (e.g. 'SKU;Price;Currency\\nA1;12.50;EUR')."

Changed5 schema fields changedOct 6, 2026

addedInput schema / properties / file

Added value: +{
+  "default": null,
+  "description": "The feed. A file the user uploaded in ChatGPT (filled in by ChatGPT; other clients use the URL).",
+  "properties": {
+    "download_url": {
+      "description": "Temporary download URL",
+      "type": "string"
+    },
+    "file_id": {
+      "description": "ChatGPT file id",
+      "type": "string"
+    },
+    "file_name": {
+      "description": "Original filename, if known",
+      "type": "string"
+    },
+    "mime_type": {
+      "description": "MIME type, if known",
+      "type": "string"
+    }
+  },
+  "required": [
+    "download_url",
+    "file_id"
+  ],
+  "title": "File",
+  "type": "object"
+}

changedInput schema / properties / file_base64 / description

Previous value: -"The feed file. File content encoded as Base64 (standard alphabet). Max 20 MiB decoded."New value: +"The feed. File content as Base64 (standard alphabet). Max 20 MiB decoded; prefer a URL or upload."

addedInput schema / properties / file_text

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The feed. The table as CSV or TSV text, header row first (e.g. 'SKU;Price;Currency\\nA1;12.50;EUR'). Use this when you can read the user's spreadsheet but cannot pass the file itself.",
+  "title": "File Text"
+}

addedInput schema / properties / file_url

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The feed. Public URL of the file (http/https). Google Drive, Google Sheets and Dropbox share links are converted to direct downloads. Max 20 MiB.",
+  "title": "File Url"
+}

changedInput schema / properties / filename / description

Previous value: -"Original filename including extension (e.g. prices.xlsx); used to detect the format."New value: +"Original filename with extension (e.g. prices.xlsx); used to detect the format."

First observedOct 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces that with 'nothing is changed' rather than contradicting it. It adds substantive behavioral detail beyond the annotations: the exact rule classes checked (required fields, GTIN check digit, price format, duplicate IDs, Shopify variants) and the shape of the reported issues (row, column, rule code, fix hint). Rate limits, auth requirements and size limits are not covered.

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?

Three dense sentences with the purpose, scope and the key output guarantee front-loaded. The long middle clause enumerating validation rules is information-rich but slightly list-heavy; still, nothing is padding and the essential facts come first.

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

Completeness5/5

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

With an output schema present, the description is not obliged to explain return values, yet it still characterizes the issue payload, which is a bonus. Combined with full schema coverage, rich annotations and the profile/options enumeration, an agent has everything needed to invoke this validator correctly.

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%, so the schema already documents every parameter including the profile enum values and the options reference. The description only restates the three transport modes (upload, URL, CSV text) at a high level and does not add format or constraint details beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Checks a product feed or catalog export') plus the target platforms (Google Merchant Center, Shopify, Meta) and the pre-upload timing. An agent can immediately tell this is a read-only feed validator and distinguish it from siblings like documents_tables and supplier_compare, which serve different purposes.

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?

The 'before upload' framing gives clear context for when to call this tool, and the accepted input formats (CSV, TSV, XLSX) and platforms narrow the use case further. It does not, however, name an alternative tool or state a when-not condition, so the routing guidance is contextual rather than explicit.

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

All Boring API tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?