Skip to main content
Glama

openapi_v2_competitors

Competitor Lookup V2

Search competitor products by keyword, brand, ASIN, or category with filters.

Use this to identify competing products around a specific listing or brand. Example: pass asin="B07FR2V8SH" to find all products competing in the same keywords and category. Data is based on the latest daily snapshot; results are paginated (max 100 per page). Related: /products/search for broader keyword discovery.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

Example Response:

{
  "success": true,
  "meta": {
    "requestId": "Requestid",
    "timestamp": "Timestamp"
  }
}

Output Schema:

{
  "properties": {
    "success": {
      "type": "boolean",
      "title": "Success",
      "description": "Whether the request was successful",
      "default": true
    },
    "data": {
      "title": "Data",
      "description": "Response data payload"
    },
    "error": {
      "description": "Error details if request failed"
    },
    "meta": {
      "description": "Metadata for API responses.\n\nCredit fields follow the ADR-0003 parallel-fields strategy (Option 3):\n- `credits_remaining` / `credits_consumed` (int): legacy fields, rounded\n  to whole credits, kept for zero-breaking-change to existing SDK clients.\n- `credits_remaining_exact` / `credits_consumed_exact` (float): new\n  precision-aware fields for clients that opt in to decimal credits.\n\nSee ADR-0003 decision 5 and the \u00a78 deprecation timeline.\n\nTODO(2026-11, ADR-0003 \u00a78 +6mo): mark `credits_remaining` /\n`credits_consumed` as `deprecated=True` in their Field() definitions\nand announce in customer changelog.\nTODO(2027-05, ADR-0003 \u00a78 +12mo): remove the legacy int fields via a\nmajor-version bump of the OpenAPI surface.",
      "properties": {
        "requestId": {
          "type": "string",
          "title": "Requestid",
          "description": "Unique request identifier"
        },
        "timestamp": {
          "type": "string",
          "title": "Timestamp",
          "description": "Response timestamp in ISO 8601 format"
        },
        "total": {
          "title": "Total",
          "description": "Total number of records"
        },
        "page": {
          "title": "Page",
          "description": "Current page number"
        },
        "pageSize": {
          "title": "Pagesize",
          "description": "Number of records per page"
        },
        "totalPages": {
          "title": "Totalpages",
          "description": "Total number of pages"
        },
        "creditsRemaining": {
          "title": "Creditsremaining",
          "description": "Remaining API credits (rounded to whole credits; see creditsRemainingExact for precise value)"
        },
        "creditsConsumed": {
          "title": "Creditsconsumed",
          "description": "Credits consumed by this request (rounded; see creditsConsumedExact for precise value)"
        },
        "creditsRemainingExact": {
          "title": "Creditsremainingexact",
          "description": "Remaining API credits, precise to 1 decimal place"
        },
        "creditsConsumedExact": {
          "title": "Creditsconsumedexact",
          "description": "Credits consumed by this request, precise to 1 decimal place"
        },
        "tokensUsage": {
          "description": "Provider token-usage block \u2014 populated on terminal video polls only, null on every non-video endpoint. See TokensUsage for its fields."
        }
      },
      "type": "object",
      "required": [
        "requestId",
        "timestamp"
      ],
      "title": "ResponseMeta"
    }
  },
  "type": "object",
  "required": [
    "meta"
  ],
  "title": "OpenApiResponse[list[Product]]",
  "examples": []
}

422: Validation Error Content-Type: application/json

Example Response:

{
  "detail": [
    {
      "loc": [],
      "msg": "Message",
      "type": "Error Type",
      "ctx": {}
    }
  ]
}

Output Schema:

{
  "properties": {
    "detail": {
      "items": {
        "properties": {
          "loc": {
            "items": {},
            "type": "array",
            "title": "Location"
          },
          "msg": {
            "type": "string",
            "title": "Message"
          },
          "type": {
            "type": "string",
            "title": "Error Type"
          },
          "input": {
            "title": "Input"
          },
          "ctx": {
            "type": "object",
            "title": "Context"
          }
        },
        "type": "object",
        "required": [
          "loc",
          "msg",
          "type"
        ],
        "title": "ValidationError"
      },
      "type": "array",
      "title": "Detail"
    }
  },
  "type": "object",
  "title": "HTTPValidationError"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asinNoAmazon Standard Identification Number (10-char alphanumeric). Example: 'B07FR2V8SH'.
pageNoPage number
badgesNoInclude products with these badges. Example: ['bestSeller', 'amazonChoice', 'newRelease', 'aPlus', 'video'].
sortByNoSort fieldmonthlySalesFloor
keywordNoSearch keyword
pageSizeNoPage size
brandNameNoFilter by brand name.
dateRangeNoAggregation window for metrics like monthly sales, revenue, and rating count. '30d' (default) — last 30 days. 'YYYY-MM' — that calendar month, e.g. '2026-04'. Available months: '2026-02' up to the most recent completed month.30d
sortOrderNoSort direction: asc or descdesc
sellerNameNoFilter by seller name.
marketplaceNoAmazon marketplace code. Only 'US' is currently supported.US
categoryPathNoCategory hierarchy from root to current level (e.g., ['Electronics', 'Computers', 'Laptops'])
fulfillmentsNoFulfillment filter. Example: ['FBA', 'FBM'].
excludeBadgesNoExclude products with these badges. Supported: ['aPlus', 'video'].
excludeBrandsNoBrand names to exclude. Example: ['Generic'].
includeBrandsNoBrand names to include. Example: ['Apple', 'Samsung'].
excludeSellersNoSeller names to exclude.
includeSellersNoSeller names to include. Example: ['Apple Store'].
sellerCountMaxNoMaximum number of sellers. Example: 20.
sellerCountMinNoMinimum number of sellers. Example: 1.
excludeKeywordsNoKeywords to exclude from results. Example: ['refurbished', 'used'].
keywordMatchTypeNoKeyword match type: 'fuzzy', 'phrase', or 'exact'. Null = fuzzy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sortBy / enum
      Previous value: -[
      -  "monthlySalesFloor",
      -  "monthlyRevenueFloor",
      -  "salesGrowthRate",
      -  "bsrGrowthRate",
      -  "bsr",
      -  "price",
      -  "rating",
      -  "ratingCount",
      -  "listingDate"
      -]New value: +[
      +  "monthlySalesFloor",
      +  "monthlyRevenueFloor",
      +  "salesGrowthRate",
      +  "bsrGrowthRate",
      +  "bsr",
      +  "price",
      +  "rating",
      +  "ratingCount",
      +  "listingDate",
      +  "grossMarginRate",
      +  "monthlyRevenueGrowthRate",
      +  "bsrGrowth"
      +]
  2. Changed5 schema fields changed
    • addedInput schema / properties / marketplace / const
      Added value: +"US"
    • changedInput schema / properties / marketplace / description
      Previous value: -"Amazon marketplace code"New value: +"Amazon marketplace code. Only 'US' is currently supported."
    • removedInput schema / properties / marketplace / enum
      Removed value: -[
      -  "US",
      -  "UK"
      -]
    • removedInput schema / properties / marketplace / x-unsupported-values
      Removed value: -[
      -  "UK"
      -]
    • changedInput schema / properties / sortBy / enum
      Previous value: -[
      -  "monthlySalesFloor",
      -  "monthlyRevenueFloor",
      -  "bsr",
      -  "price",
      -  "rating",
      -  "ratingCount",
      -  "listingDate"
      -]New value: +[
      +  "monthlySalesFloor",
      +  "monthlyRevenueFloor",
      +  "salesGrowthRate",
      +  "bsrGrowthRate",
      +  "bsr",
      +  "price",
      +  "rating",
      +  "ratingCount",
      +  "listingDate"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / dateRange / description
      Previous value: -"Aggregation window for metrics like monthly sales, revenue, and rating count. '30d' (default) — last 30 days. 'YYYY-MM' — that calendar month, e.g. '2026-04'. Available months: '2026-02' up to the most recent completed month.\n\n聚合窗口(月销量、月营收、月评论数等指标)。'30d'(默认)— 最近 30 天。'YYYY-MM' — 该自然月,如 '2026-04'。可选月份:'2026-02' 至最近一个已完结的月份。"New value: +"Aggregation window for metrics like monthly sales, revenue, and rating count. '30d' (default) — last 30 days. 'YYYY-MM' — that calendar month, e.g. '2026-04'. Available months: '2026-02' up to the most recent completed month."
  4. Changed1 schema field changed
    • changedInput schema / properties / dateRange / description
      Previous value: -"Time range filter. Relative ('30d') or month ('2026-01'). Default '30d'."New value: +"Aggregation window for metrics like monthly sales, revenue, and rating count. '30d' (default) — last 30 days. 'YYYY-MM' — that calendar month, e.g. '2026-04'. Available months: '2026-02' up to the most recent completed month.\n\n聚合窗口(月销量、月营收、月评论数等指标)。'30d'(默认)— 最近 30 天。'YYYY-MM' — 该自然月,如 '2026-04'。可选月份:'2026-02' 至最近一个已完结的月份。"
  5. Changed1 schema field changed
    • changedInput schema / properties / pageSize / description
      Previous value: -"Page size (max 100)"New value: +"Page size"
  6. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that data is based on the latest daily snapshot and that results are paginated (max 100 per page). It also implies a read-only operation via the response schema. These are useful behavioral details, though it doesn't cover authentication, rate limits, or specific side effects (likely none for a search). It adds value beyond the schema.

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?

The core prose is concise and front-loaded with purpose and example. However, the overall description block includes large embedded response schemas (200 and 422) that are redundant given the separate output schema fields. This bloats the definition and reduces conciseness, though the key information is upfront.

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 complex tool with 22 parameters, the description covers the main use case, pagination, and snapshot behavior. It includes an example that clarifies usage. While it doesn't explain every filter in prose, the schema provides those details. The description is sufficient for an agent to select and invoke the tool correctly, though it could mention return value structure more explicitly.

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 input schema already provides descriptions for all 22 parameters (100% coverage). The description only adds an example use of the 'asin' parameter, which is more about usage than parameter semantics. Since the schema fully documents each parameter, the description adds minimal extra meaning, meeting the baseline of 3.

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 clearly states the tool's function: 'Search competitor products by keyword, brand, ASIN, or category with filters.' It gives a concrete example with an ASIN and differentiates from a sibling tool by noting 'Related: /products/search for broader keyword discovery.' This is specific and distinguishes it from other search tools.

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?

The description explains when to use it: 'Use this to identify competing products around a specific listing or brand.' It also mentions an alternative for broader searches, implying when not to use it. However, it doesn't explicitly state conditions like 'use this instead of products_search when you need competitor context,' so it's clear but not exhaustive.

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