Skip to main content
Glama

Herofab marketplace image rules

Check an image against marketplace rules

check_image_spec
Read-onlyIdempotent

Check an image's width, height, format and file size, and its declared main-image background and product fill, against a platform's published rules. Returns pass, the failing rules, notes, the rules that need the photo itself, and a link to fix the image.

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": {
      "platform": "<platform>",
      "width": "<width>",
      "height": "<height>",
      "format": "<format>"
    },
    "name": "check_image_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYesImage width in pixels.
formatYesFile format.
heightYesImage height in pixels.
platformYesPlatform key (see get_image_requirements).
backgroundNoMain-image background as seen in the photo: pure-white (RGB 255), white (off-white), light (light grey or neutral), coloured (plain colour), busy (scene or texture), transparent.
product_fillNoShare of the frame the product covers on its longest axis, 0 to 1 (0.85 = 85%).
file_size_bytesNoFile size in bytes; without it the file size limit is not checked.

Output Schema

NameRequiredDescriptionDefault
nameYes
passYesTrue when no checked rule fails; see not_checked for what was not checked.
failsYes
notesYes
fix_urlYesWhere to fix a failing image; null when nothing fails.
platformYes
guide_urlYes
not_checkedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add nuance — and it does: it discloses that results include rules that cannot be evaluated from metadata alone ("the rules that need the photo itself"), which is a genuine limitation an agent must know before trusting a pass. The return shape (pass, failing rules, notes, fix link) is also described. It does not state what happens for unsupported platform/format combinations, keeping it below 5.

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, zero filler: the first front-loads what is checked and against what, the second front-loads what comes back. Every clause corresponds to a distinct piece of information an agent needs before calling.

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?

With an output schema present, the description need not explain return values, yet it still summarizes them usefully and flags the photo-dependent rules that limit a metadata-only check. For a 7-parameter read-only validator this is close to complete; the only missing piece is explicit guidance on when to reach for get_image_requirements instead.

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 every parameter is already documented with units, ranges, and enum meanings, so the schema carries the semantic load and 3 is the baseline. The description adds one meaningful distinction — that background and product fill are *declared* values rather than measured ones — but it does not explain the omission-tolerant behavior of file_size_bytes or the interaction between background and transparent formats beyond what the schema says.

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 names a specific verb (check) and resource (image) and enumerates exactly which attributes are validated — width, height, format, file size, plus the declared background and product fill — against a named platform's published rules. It is clearly distinct from a requirements-lookup tool. It stops short of naming get_image_requirements as the sibling it is not, so it lands at 4 rather than 5.

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: an agent can infer this is the validation step that follows knowing a platform's rules. There is no explicit "use this when..." or "do not use this when..." statement, and the sibling get_image_requirements is not referenced (only the schema's platform parameter points at it). Adequate but with a real routing gap.

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