Skip to main content
Glama

openapi_v2_product_traffic_terms

Get product traffic terms

  1. Function

Return the target ASIN's traffic-keyword list for a single weekly snapshot, with filtering, sorting and pagination. Includes impression points, positions, traffic shares, estimated searches and ABA ranks; resolvedDate is the actual snapshot date. This is current-period discovery data, not a trend or time-series endpoint.

  1. Use cases

Discover the target ASIN's current traffic-driving keywords, for either your own product or a competitor. Then pass selected keywords to product-traffic-terms-trend for their weekly history, or use product-traffic-trend for ASIN-level weekly totals.

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": {
      "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[AsinKeywordsData]",
  "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
asinYesAmazon Standard Identification Number (10-character alphanumeric).
dateYesLookup date (YYYY-MM-DD). Returns the latest snapshot on or before this date; actual date is `resolvedDate`.
pageNoPage number, starting at 1.
sortByNoSort field: trafficShare=ASIN keyword-traffic share; estimateImpressionPoint=estimated impressions; absolutePosition=SERP position; avgPosition=average position; latestObservedAt=latest observation; keywordEstimateSearchCount=estimated searches; keywordAbaRank=numeric ABA rank; keyword=lexical order.trafficShare
pageSizeNoItems per page; 1 to 100.
sortOrderNoSort direction.desc
granularityNoData period granularity. Only `week` is currently supported.week
marketplaceNoAmazon marketplace code. Only 'US' is currently supported.US
exploreTypesNoOptional placement filter. Empty means all result types. Allowed values: ORG/SP/SB/SBV/SPR.
keywordContainsNoNon-empty substring filter for returned keywords; omit to disable this filter.
keywordAbaRankMaxNoMaximum numeric keyword ABA rank; must not be below keywordAbaRankMin.
keywordAbaRankMinNoMinimum numeric keyword ABA rank; must not exceed keywordAbaRankMax.
keywordEstimateSearchCountMaxNoMaximum estimated keyword search count; must not be below keywordEstimateSearchCountMin.
keywordEstimateSearchCountMinNoMinimum estimated keyword search count; must not exceed keywordEstimateSearchCountMax.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed28 schema fields changed
    • addedInput schema / properties / asin / maxLength
      Added value: +10
    • addedInput schema / properties / asin / minLength
      Added value: +10
    • addedInput schema / properties / asin / pattern
      Added value: +"^[A-Za-z0-9]{10}$"
    • changedInput schema / properties / date / description
      Previous value: -"Lookup date in YYYY-MM-DD format. The response returns the latest snapshot on or before this date."New value: +"Lookup date (YYYY-MM-DD). Returns the latest snapshot on or before this date; actual date is `resolvedDate`."
    • addedInput schema / properties / date / format
      Added value: +"date"
    • addedInput schema / properties / date / pattern
      Added value: +"^\\d{4}-(0[1-9]|1[0-2])-([0-2]\\d|3[01])$"
    • removedInput schema / properties / exploreTypes / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "enum": [
      -        "ORG",
      -        "SP",
      -        "SB",
      -        "SBV",
      -        "SPR"
      -      ],
      -      "type": "string"
      -    },
      -    "type": "array"
      -  }
      -]
    • addedInput schema / properties / exploreTypes / items
      Added value: +{
      +  "enum": [
      +    "ORG",
      +    "SP",
      +    "SB",
      +    "SBV",
      +    "SPR"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / granularity
      Added value: +{
      +  "const": "week",
      +  "default": "week",
      +  "description": "Data period granularity. Only `week` is currently supported.",
      +  "title": "granularity",
      +  "type": "string"
      +}
    • removedInput schema / properties / keywordAbaRankMax / anyOf
      Removed value: -[
      -  {
      -    "minimum": 1,
      -    "type": "integer"
      -  }
      -]
    • changedInput schema / properties / keywordAbaRankMax / description
      Previous value: -"Maximum numeric keyword ABA rank."New value: +"Maximum numeric keyword ABA rank; must not be below keywordAbaRankMin."
    • addedInput schema / properties / keywordAbaRankMax / minimum
      Added value: +1
    • removedInput schema / properties / keywordAbaRankMin / anyOf
      Removed value: -[
      -  {
      -    "minimum": 1,
      -    "type": "integer"
      -  }
      -]
    • changedInput schema / properties / keywordAbaRankMin / description
      Previous value: -"Minimum numeric keyword ABA rank."New value: +"Minimum numeric keyword ABA rank; must not exceed keywordAbaRankMax."
    • addedInput schema / properties / keywordAbaRankMin / minimum
      Added value: +1
    • removedInput schema / properties / keywordContains / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  }
      -]
    • changedInput schema / properties / keywordContains / description
      Previous value: -"Optional substring filter for returned keywords."New value: +"Non-empty substring filter for returned keywords; omit to disable this filter."
    • addedInput schema / properties / keywordContains / minLength
      Added value: +1
    • addedInput schema / properties / keywordContains / pattern
      Added value: +"\\S"
    • removedInput schema / properties / keywordEstimateSearchCountMax / anyOf
      Removed value: -[
      -  {
      -    "minimum": 0,
      -    "type": "integer"
      -  }
      -]
    • changedInput schema / properties / keywordEstimateSearchCountMax / description
      Previous value: -"Maximum estimated keyword search count."New value: +"Maximum estimated keyword search count; must not be below keywordEstimateSearchCountMin."
    • addedInput schema / properties / keywordEstimateSearchCountMax / minimum
      Added value: +0
    • removedInput schema / properties / keywordEstimateSearchCountMin / anyOf
      Removed value: -[
      -  {
      -    "minimum": 0,
      -    "type": "integer"
      -  }
      -]
    • changedInput schema / properties / keywordEstimateSearchCountMin / description
      Previous value: -"Minimum estimated keyword search count."New value: +"Minimum estimated keyword search count; must not exceed keywordEstimateSearchCountMax."
    • addedInput schema / properties / keywordEstimateSearchCountMin / minimum
      Added value: +0
    • changedInput schema / properties / page / description
      Previous value: -"Page number."New value: +"Page number, starting at 1."
    • changedInput schema / properties / pageSize / description
      Previous value: -"Page size."New value: +"Items per page; 1 to 100."
    • changedInput schema / properties / sortBy / description
      Previous value: -"Sort field."New value: +"Sort field: trafficShare=ASIN keyword-traffic share; estimateImpressionPoint=estimated impressions; absolutePosition=SERP position; avgPosition=average position; latestObservedAt=latest observation; keywordEstimateSearchCount=estimated searches; keywordAbaRank=numeric ABA rank; keyword=lexical order."
  2. Changed1 schema field changed
    • removedInput schema / properties / granularity
      Removed value: -{
      -  "default": "week",
      -  "description": "Period granularity. Supports `day`, `week`, and `month`.",
      -  "enum": [
      -    "day",
      -    "week",
      -    "month"
      -  ],
      -  "title": "granularity",
      -  "type": "string"
      -}
  3. Changed8 schema fields changed
    • addedInput schema / properties / keywordAbaRankMax
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 1,
      +      "type": "integer"
      +    }
      +  ],
      +  "description": "Maximum numeric keyword ABA rank.",
      +  "title": "keywordAbaRankMax",
      +  "type": "integer"
      +}
    • addedInput schema / properties / keywordAbaRankMin
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 1,
      +      "type": "integer"
      +    }
      +  ],
      +  "description": "Minimum numeric keyword ABA rank.",
      +  "title": "keywordAbaRankMin",
      +  "type": "integer"
      +}
    • addedInput schema / properties / keywordEstimateSearchCountMax
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  ],
      +  "description": "Maximum estimated keyword search count.",
      +  "title": "keywordEstimateSearchCountMax",
      +  "type": "integer"
      +}
    • addedInput schema / properties / keywordEstimateSearchCountMin
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  ],
      +  "description": "Minimum estimated keyword search count.",
      +  "title": "keywordEstimateSearchCountMin",
      +  "type": "integer"
      +}
    • 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"
      -]
    • changedInput schema / properties / sortBy / enum
      Previous value: -[
      -  "trafficShare",
      -  "estimateImpressionPoint",
      -  "absolutePosition",
      -  "avgPosition",
      -  "latestObservedAt",
      -  "keyword"
      -]New value: +[
      +  "trafficShare",
      +  "estimateImpressionPoint",
      +  "absolutePosition",
      +  "avgPosition",
      +  "latestObservedAt",
      +  "keywordEstimateSearchCount",
      +  "keywordAbaRank",
      +  "keyword"
      +]
  4. Changed6 schema fields changed
    • removedInput schema / properties / granularity / const
      Removed value: -"lately_day"
    • changedInput schema / properties / granularity / default
      Previous value: -"lately_day"New value: +"week"
    • changedInput schema / properties / granularity / description
      Previous value: -"Observation-window granularity. ASIN traffic terms currently support `lately_day` only."New value: +"Period granularity. Supports `day`, `week`, and `month`."
    • addedInput schema / properties / granularity / enum
      Added value: +[
      +  "day",
      +  "week",
      +  "month"
      +]
    • removedInput schema / properties / lookbackDays
      Removed value: -{
      -  "const": 7,
      -  "default": 7,
      -  "description": "Observation-window length in days. Currently only `7` is supported.",
      -  "title": "lookbackDays",
      -  "type": "integer"
      -}
    • changedInput schema / properties / sortBy / enum
      Previous value: -[
      -  "trafficShare",
      -  "estimateImpressionPoint",
      -  "absolutePosition",
      -  "avgPosition",
      -  "keywordEstimateSearchCount",
      -  "keywordAbaRank",
      -  "latestObservedAt",
      -  "keyword"
      -]New value: +[
      +  "trafficShare",
      +  "estimateImpressionPoint",
      +  "absolutePosition",
      +  "avgPosition",
      +  "latestObservedAt",
      +  "keyword"
      +]
  5. Changed6 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"Lookup date in YYYY-MM-DD format. Data is stored as daily snapshots for the most recent 7 days, and the response returns the latest snapshot on or before this date."New value: +"Lookup date in YYYY-MM-DD format. The response returns the latest snapshot on or before this date."
    • changedInput schema / properties / exploreTypes / description
      Previous value: -"Optional placement filter. Empty means all result types."New value: +"Optional placement filter. Empty means all result types. Allowed values: ORG/SP/SB/SBV/SPR."
    • addedInput schema / properties / granularity
      Added value: +{
      +  "const": "lately_day",
      +  "default": "lately_day",
      +  "description": "Observation-window granularity. ASIN traffic terms currently support `lately_day` only.",
      +  "title": "granularity",
      +  "type": "string"
      +}
    • addedInput schema / properties / lookbackDays
      Added value: +{
      +  "const": 7,
      +  "default": 7,
      +  "description": "Observation-window length in days. Currently only `7` is supported.",
      +  "title": "lookbackDays",
      +  "type": "integer"
      +}
    • changedInput schema / properties / sortBy / default
      Previous value: -"estimateImpressionPoint"New value: +"trafficShare"
    • changedInput schema / properties / sortBy / enum
      Previous value: -[
      -  "estimateImpressionPoint",
      -  "absolutePosition",
      -  "avgPosition",
      -  "keywordEstimateSearchCount",
      -  "keywordAbaRank",
      -  "observedAt",
      -  "keyword"
      -]New value: +[
      +  "trafficShare",
      +  "estimateImpressionPoint",
      +  "absolutePosition",
      +  "avgPosition",
      +  "keywordEstimateSearchCount",
      +  "keywordAbaRank",
      +  "latestObservedAt",
      +  "keyword"
      +]
  6. Changed9 schema fields changed
    • changedInput schema / properties / asin / description
      Previous value: -"亚马逊 ASIN,10 位字母数字编码"New value: +"Amazon Standard Identification Number (10-character alphanumeric)."
    • changedInput schema / properties / date / description
      Previous value: -"查询日期,格式 YYYY-MM-DD。数据按天快照存储,保留最近 7 天,返回该日期当日或之前最近一个快照数据。"New value: +"Lookup date in YYYY-MM-DD format. Data is stored as daily snapshots for the most recent 7 days, and the response returns the latest snapshot on or before this date."
    • changedInput schema / properties / exploreTypes / description
      Previous value: -"可选的曝光位置筛选;为空时表示返回全部位置类型"New value: +"Optional placement filter. Empty means all result types."
    • changedInput schema / properties / keywordContains / description
      Previous value: -"返回关键词的可选包含词筛选"New value: +"Optional substring filter for returned keywords."
    • changedInput schema / properties / marketplace / description
      Previous value: -"亚马逊站点代码"New value: +"Amazon marketplace code"
    • changedInput schema / properties / page / description
      Previous value: -"页码,从 1 开始"New value: +"Page number."
    • changedInput schema / properties / pageSize / description
      Previous value: -"每页条数,最大 100"New value: +"Page size."
    • changedInput schema / properties / sortBy / description
      Previous value: -"排序字段"New value: +"Sort field."
    • changedInput schema / properties / sortOrder / description
      Previous value: -"排序方向"New value: +"Sort direction."
  7. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are present, so the description carries the disclosure burden. It clarifies the snapshot nature (single weekly resolved date vs trend), lists returned fields (impressions, positions, estimated searches, ABA rank), and flags the granularity constraint. It does not disclose auth requirements, rate limits, empty-result behavior, or whether results for a brand-new ASIN may be absent — modest but not severe gaps.

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?

Compact two-section layout (Function / Use cases) with a short rationale sentence. The embedded response example and schema are relevant. It stays readable and avoids boilerplate, though a couple of lines are spent restating generic wrapper fields.

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?

Covers the resource, the snapshot-vs-trend distinction, the resolved date concept, filtering/sorting/pagination, and follow-on usage. Notable gap: the required 'target ASIN' and 'date' inputs are not visible in the given schema, and the response example omits the data payload — but the surrounding text still conveys the essentials for a correct call.

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?

Input schema coverage is 100% with per-parameter descriptions and constraints. The description adds context by mentioning filtering, sorting, and pagination, but the parameter meanings largely come from the schema. No penalty for duplication, but no added semantic value beyond the schema either.

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?

States a precise verb+resource+mode: returns the target ASIN's traffic keywords for a single weekly snapshot, with sorting/filter/pagination, and explicitly says it is not a trend/time-series endpoint. Names the exact sibling (product_traffic_terms_trend) it is not, so there is no ambiguity.

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?

Provides a dedicated 'Use cases' section: tells the agent to use it for current-period traffic keywords, and routes to product_traffic_terms_trend for per-keyword history or product_traffic_trend for weekly totals. It does not list prerequisites (e.g. required asin/date), but the when-to-use guidance is clear and actionable.

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