Skip to main content
Glama
Sign In

Shootika

by com.shootika
OverviewDiscussionsAdmin

Add product

add_product

Adds a product to the store's Shootika catalog, optionally with photos fetched from public image URLs. Use it when a product to shoot is not in list_products yet. The product is created even when a photo cannot be fetched; those come back in images_failed. Not available on Shopify stores: their products come from Shopify, so add the product there instead.

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": {
      "title": "<title>"
    },
    "name": "add_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesThe product name.
familyNoWhat the product is, when the title does not say: apparel, footwear, accessories, beauty, home, electronics, sports, food or other. Shootika derives it from the title otherwise.
image_urlsNoUp to 10 public image URLs (PNG, JPEG or WebP) to add as its photos.
external_idNoThe store's own id for the product (a SKU, say). Must be unique.
accessory_kindNoFor accessories and footwear only: bag, shoes, eyewear, watch or jewelry. A bag or shoes can also be shot on a model.
garment_categoryNoFor apparel only: tops, bottoms or one-pieces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / accessory_kind
      Added value: +{
+  "description": "For accessories and footwear only: bag, shoes, eyewear, watch or jewelry. A bag or shoes can also be shot on a model.",
+  "enum": [
+    "bag",
+    "shoes",
+    "eyewear",
+    "watch",
+    "jewelry"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / family
      Added value: +{
+  "description": "What the product is, when the title does not say: apparel, footwear, accessories, beauty, home, electronics, sports, food or other. Shootika derives it from the title otherwise.",
+  "enum": [
+    "apparel",
+    "footwear",
+    "accessories",
+    "beauty",
+    "home",
+    "electronics",
+    "sports",
+    "food",
+    "other"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / garment_category / description
      Previous value: -"What kind of garment it is: tops, bottoms or one-pieces."New value: +"For apparel only: tops, bottoms or one-pieces."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing partial-failure semantics: the product is still created when an image fetch fails, and those URLs are reported back in images_failed. It also discloses a platform-level availability constraint (Shopify stores). It does not mention auth requirements or what happens on duplicate external_id conflicts, so not a full 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?

Three tight sentences with no filler: capability first, usage trigger second, platform exclusion last. The most decision-relevant information (Shopify unsupported) is placed at the end where it reads as a caveat but is still easy to find.

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?

For a 6-parameter create tool with full schema coverage and no output schema, the description supplies the missing pieces an agent needs: when to call it, the platform restriction, and the images_failed return behavior on partial failure. Nothing essential is left unstated.

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 three of six parameters carry enums with documented meanings, so the schema already does the heavy lifting on title, family, image_urls, external_id, accessory_kind and garment_category. The description adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

Opens with a specific verb and resource ('Adds a product to the store's Shootika catalog') and immediately scopes the optional photo behavior. This is clearly distinguishable from the sibling add_product_image (which adds photos to an existing product) and from list_products.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the trigger condition ('when a product to shoot is not in list_products yet') and names a hard exclusion with a redirect: not available on Shopify stores, where the product must be created in Shopify. Both when-to-use and when-not-to-use are covered.

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

All Shootika toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources