Skip to main content
Glama

Herofab marketplace image rules

Marketplace image requirements

get_image_requirements
Read-onlyIdempotent

Official product-image rules of a marketplace or ad platform (size, file size, formats, main-image background and fill), each read from the platform's own help page, with the source and the day it was read. Omit platform to list all platforms.

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": "get_image_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoPlatform key, for example amazon, ebay, etsy, shopify, google-shopping, zalando. Omit to list every platform.

Output Schema

NameRequiredDescriptionDefault
kindNo
nameNo
rulesNo
limitsNo
checkedNoDay the official page was read (YYYY-MM-DD).
summaryNo
platformNo
guide_urlNo
platformsNoPresent when no platform was given.
main_imageNo
source_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description does add genuine context beyond them: each rule is read from the platform's own help page and accompanied by source and read date, telling the agent the data is authoritative but time-stamped. It stops short of anything about caching, coverage gaps, or behavior for unsupported platforms.

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, front-loaded with what the tool returns and how the optional filter behaves. The parenthetical field list is dense but each item is informative; nothing is wasted.

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?

An output schema exists, so return-shape explanation is unnecessary, and provenance is disclosed. The remaining gap is the unstated relationship to check_image_spec, which matters for routing in a two-tool family.

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% and the enum's own description already says "Omit to list every platform," which the description repeats almost verbatim. The single parameter therefore gains no meaning beyond the schema, so the baseline applies.

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 and resource plus the exact fields returned (size, file size, formats, main-image background and fill), so the agent knows this is a rule-lookup tool. It does not name or contrast with the sibling check_image_spec, so the retrieval-vs-validation distinction is left implicit.

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 only explicit guidance is "Omit platform to list all platforms," which is real but narrowly about one parameter. There is no statement of when to reach for this versus check_image_spec, nor of any prerequisites.

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