Skip to main content
Glama

SEO Rank Fixer

Products in Google

product_listings
Read-onlyIdempotent

For online stores (Shopify and others): one site's Google product results from Search Console (clicks and impressions as merchant listings and product snippets, last 28 days against the 28 before, and the product pages gaining or losing them), and the product pages of the latest crawl: how many can show as product snippets (stars, price) and in merchant listings (Shopping tab), what each is missing (price, image, shipping, returns, brand and codes, variant grouping) and ready-to-paste Product JSON-LD. Also the saved Merchant Center product feed compared with the pages (price and stock mismatches, broken links, missing images, brand or GTIN), and shopping questions asked to AI assistants: whether they name the store or its products and who they suggest instead, with suggested shopping questions. Read-only.

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": {
      "siteId": "<siteId>"
    },
    "name": "product_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bare 'Read-only' at the end is redundant. What the description does add is genuinely behavioral: the 28-days-vs-prior-28-days comparison window, the fact that results combine Search Console data with the latest crawl and a saved Merchant Center feed, and the specific mismatch classes reported. It stops short of stating what happens when the feed or crawl is absent, which for a multi-source composite is a notable gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

All the content is substantive — four distinct data domains — but it is delivered as one long run-on sentence stitched together with parentheses and commas. Front-loading is weak: the Search Console block leads, but the crawl, feed, and AI-question blocks are buried mid-sentence, making it hard to scan which outputs are actually returned.

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 no output schema and four heterogeneous data sources, the description carries the burden of explaining return content and does so thoroughly — snippet eligibility, missing attributes, JSON-LD availability, feed mismatches, AI assistant citations. Missing only prerequisites and any sense of response volume or pagination.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself pointing to 'a site id from list_sites'. The description adds nothing about siteId, which is acceptable given the single trivial parameter, so the baseline of 3 applies rather than a penalty.

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 the resource precisely: one site's Google product results from Search Console, crawl-time product snippet/merchant listing eligibility, comparison against a saved Merchant Center feed, and AI shopping questions. An agent can tell this is a product-listing-specific report rather than a general performance or audit tool. However, there is no explicit verb framing ('returns/reports') and no naming of the sibling tool it replaces, so differentiation from search_report or site_audit is inferred rather than stated.

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 opening clause 'For online stores (Shopify and others)' gives an audience-based usage signal, implying this is the right tool when the site sells products. There is no explicit when-not-to-use guidance, no mention of prerequisites (a connected Merchant Center feed or a completed crawl), and no routing to alternatives for non-ecommerce sites.

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.