Skip to main content
Glama

Loblaw-banner grocery prices (No Frills, Superstore, Loblaws...)

loblaws_grocery_prices
Read-only

Search grocery prices across 14 Loblaw banners by keyword, store, postal code or city; get sale prices, unit prices, deals, PC Optimum points and stock for comparison.

Instructions

Search grocery products by keyword across the 14 Loblaw banners (Loblaws, No Frills, Real Canadian Superstore, Maxi, Zehrs and others) at a chosen store, postal code or city. Returns price, sale and unit price, deals, PC Optimum points when offered, and stock. Use it for Canadian grocery price comparison, meal-cost estimates or deal tracking. 'keywords' is required. Runs the Apify Actor loudtzu/loblaws-grocery-prices on your own Apify account (pay per event: $0.0005 per product, billed by Apify; Apify platform usage may apply). Store page: https://apify.com/loudtzu/loblaws-grocery-prices

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": {
      "keywords": "<keywords>"
    },
    "name": "loblaws_grocery_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity. Used when Store number and Postal code are empty: picks a store of this banner in this city.
bannerNoStore banner. Which Loblaw chain to search.loblaw
storeIdNoStore number. 4-digit store number (shown in the store page URL on the banner website). Prices and stock are for this store. Leave empty to use Postal code or City.
fetchAllNoFetch all results. Ignore Max products and save everything (up to 50,000).
keywordsYesSearch terms. Products to search for, e.g. milk, eggs, bread. Example: ["milk","eggs"]
languageNoLanguage. Language of names and descriptions.en
maxItemsNoMax products. Total products to save across all search terms (split evenly).
postalCodeNoPostal code. Used when Store number is empty: picks the store of this banner whose postal code matches yours most closely (same first letters). Not a distance search.
runOptionsNoOptional run limits (not passed to the Actor). maxTotalChargeUsd caps what this single call can cost you on Apify.
skipSponsoredNoSkip sponsored products. Leave out products marked Sponsored (not charged).
maxItemsPerQueryNoMax products per search term. Optional fixed limit per search term. 0 = split Max products evenly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/non-destructive; the description goes considerably further by disclosing that the tool runs an Apify Actor on the caller's own account, that billing is per event at $0.0005 per product with possible platform usage, and that a run-level charge cap applies. It also describes what is returned (price, sale, unit price, deals, points, stock), which is required disclosure since there is no output schema.

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?

The opening sentence front-loads the resource and scope, followed by return contents, use cases, the required-parameter note, and then cost/runtime context. Every sentence carries information, though the pricing and billing sentence plus the store URL make it denser than strictly necessary for a 5.

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?

For an 11-parameter tool with a nested runOptions object and no output schema, the description covers purpose, returns, cost, and the required flag adequately. It leaves location-resolution precedence and per-parameter behavior to the very thorough schema, which is a defensible division of labor but not fully self-contained.

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?

With 100% schema description coverage the baseline is 3, but the description itself adds almost nothing parameter-specific beyond restating that 'keywords' is required. It does not clarify the storeId/postalCode/city precedence rules, the banner enum, or how maxItems splits across terms — it leaves all of that entirely to the schema.

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?

The description states a specific verb and resource ('Search grocery products by keyword') plus precise scope: 14 named Loblaw banners, resolved to a chosen store, postal code, or city. It also enumerates the return contents (price, sale, unit price, deals, PC Optimum points, stock), which lets an agent distinguish it from bestbuy_ca_product_search or Shopify/WooCommerce product tools without opening any schema.

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?

It gives concrete selection contexts — 'Canadian grocery price comparison, meal-cost estimates or deal tracking' — and states the hard prerequisite that 'keywords' is required. It never states when NOT to use it or names a sibling alternative, so it falls short of a 5, but the usage context is clear rather than merely implied.

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