Skip to main content
Glama
Sign In
merch-connector

merch-connector

by grahamton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

scrape_pdp

Extract key product page data: title, description fill rate, images, reviews, schema, spec table, cross-sells, CTAs, prices, badges, and performance timing from any single product URL.

Instructions

Scrape a product detail page (PDP) and return PDP-specific signals: title, description fill rate, image count, review presence and count, review schema (ld+json), spec table, cross-sell modules, CTA text, primary and original prices, badge texts, and performance timing. Use this instead of scrape_page when the target is a single product page.

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": {
      "url": "<url>"
    },
    "name": "scrape_pdp"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull http/https URL of the PDP to scrape.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the output signals including performance timing, but does not explicitly state read-only behavior, potential failure modes, or any side effects. This is adequate but not comprehensive.

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, direct, no filler. The first sentence states purpose and lists outputs; the second provides usage guidance.

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 a single-parameter tool with no output schema, the description covers the purpose, key outputs, and usage distinction. It lacks explicit return structure but is reasonably complete.

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?

The schema has one param 'url' with a clear description, and schema coverage is 100%. The description adds context that the URL should be a PDP, but parameters are well-documented in the schema, so baseline 3 is appropriate.

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 uses the specific verb 'scrape' and identifies the resource as 'product detail page (PDP)', listing concrete signals returned. It explicitly distinguishes from sibling scrape_page by naming it and stating when to use this alternative.

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?

The description explicitly states 'Use this instead of scrape_page when the target is a single product page,' providing a clear alternative and condition. This satisfies the 'when/when-not/alternatives' criterion.

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

Deploy Server

Other Tools