Skip to main content
Glama

BRAINIAC E-commerce Catalog Intelligence

Audit product image metadata

ecommerce-catalog_product-image-metadata-audit

Check supplied image URLs, alt text, filename extensions, and supplied pixel sizes. Image files are not downloaded and alt text is not generated. Price $0.03 USDC. POST /api/v1/ecommerce-catalog/product-image-metadata-audit. Unpaid calls return 402 and do not run.

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": "ecommerce-catalog_product-image-metadata-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
productsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and discharges much of it: it discloses that files are not downloaded, that alt text is not generated (so it is a static inspection, not an enrichment), the exact price of $0.03 USDC, the HTTP endpoint, and the 402 failure behavior for unpaid calls. It stops short of describing the response payload or whether partial failures are reported per product.

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?

Four short sentences, purpose front-loaded, followed by scope exclusions, then cost/endpoint/payment behavior. Nothing is padding, though the raw POST route adds little for an agent that cannot call it directly.

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?

This is a complex tool: four input channels, deeply nested product objects with ~30 fields, no output schema, and no annotations. The description covers what is checked and the payment model but leaves the agent unable to tell how to supply data (inline JSON vs CSV vs base64 file vs array) or what the audit returns.

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 0% across four top-level parameters, so the description must compensate and largely does not. It alludes to the fields being audited (URL, alt text, extension, pixel size), which loosely maps to products[].imageUrl/imageAlt/imageWidth/imageHeight, but it never explains the csv/json/file/products input modes or whether they are mutually exclusive alternatives.

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?

States a specific verb ('Check') and enumerates the exact resources examined: image URLs, alt text, filename extensions, and supplied pixel sizes. That is far more concrete than the sibling names suggest on their own, though the description never positions itself against alternatives such as product-feed-validate, which also touches image fields.

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 only implied by 'supplied' data and by the negative scope ('Image files are not downloaded and alt text is not generated'). There is no explicit statement of when to choose this over the feed validator or health report, and no prerequisites beyond the payment note.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources