Skip to main content
Glama

openapi_v2_keyword_market_profile

Get keyword market profile

  1. Function

Return six graded market dimensions with raw business evidence, observed ad coverage and annual seasonality at marketProfile.annualSeasonality for one or more keywords, using the latest available snapshot on or before date. Read level and interpretation for the category, and levelEvidence for the underlying values. Ad coverage is the fraction of distinct observed products seen in sponsored placements, not ad spend or impression share. No normalized scores are returned. Results preserve request keyword order in data.context + data.items[], including single-keyword requests.

  1. Use cases

Compare demand, concentration, organic entry conditions, supply, brands and product benchmarks. Directions describe numeric meaning, not a recommendation to enter or avoid a market. Annual seasonality is a historical estimate of a keyword characteristic, independent of the selected trend window, and may change as history changes. Use trend-profile with windowPeriods for window-specific volatility; use detail for additional snapshot metrics and trend for raw weekly history.

  1. Results and billing

Each request keyword keeps its position and identity.keyword in data.items. Only available dimensions and evidence are returned. An item without a profile contains only identity. Zero is a measured value; an empty peakPeriods array means no peak was identified in available evidence. Each item containing marketProfile costs one credit; identity-only items cost zero. Balance is prechecked for the requested keyword count; actual charge is in meta.creditsConsumedExact. context.resolvedDate is the actual snapshot date when known; dataWindow.currentPeriod is its period, not the historical range used by annual seasonality. Historical peaks do not imply yearly recurrence; non_seasonal may still include peakPeriods.

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[KeywordMarketProfileData]",
  "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

NameRequiredDescriptionDefault
dateYesLookup date (YYYY-MM-DD). Returns the latest profile on or before this date; actual date is `resolvedDate`.
keywordNoSingle keyword; mutually exclusive with `keywords`. Surrounding whitespace is trimmed; letter case is accepted.
keywordsNoKeyword list, up to 20; mutually exclusive with `keyword`. Must equal `LOWER(TRIM(value))`; uppercase letters and surrounding whitespace are rejected. Duplicate keywords are rejected.
granularityNoData period granularity. Only `week` is currently supported.week
marketplaceNoAmazon marketplace code. Only 'US' is currently supported.US

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • addedInput schema / oneOf
      Added value: +[
      +  {
      +    "required": [
      +      "keyword"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "keywords"
      +    ]
      +  }
      +]
    • changedInput schema / properties / date / description
      Previous value: -"Lookup date in YYYY-MM-DD format. Returns the latest weekly snapshot on or before this date."New value: +"Lookup date (YYYY-MM-DD). Returns the latest profile 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])$"
    • 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 / keyword / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  }
      -]
    • changedInput schema / properties / keyword / description
      Previous value: -"Keyword to look up."New value: +"Single keyword; mutually exclusive with `keywords`. Surrounding whitespace is trimmed; letter case is accepted."
    • addedInput schema / properties / keyword / minLength
      Added value: +1
    • addedInput schema / properties / keyword / pattern
      Added value: +"\\S"
    • removedInput schema / properties / keywords / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "maxItems": 20,
      -    "minItems": 1,
      -    "type": "array"
      -  }
      -]
    • changedInput schema / properties / keywords / description
      Previous value: -"Keywords to look up in batch, up to 20."New value: +"Keyword list, up to 20; mutually exclusive with `keyword`. Must equal `LOWER(TRIM(value))`; uppercase letters and surrounding whitespace are rejected. Duplicate keywords are rejected."
    • addedInput schema / properties / keywords / items
      Added value: +{
      +  "minLength": 1,
      +  "pattern": "^[^A-Z\\s](?:[^A-Z]*[^A-Z\\s])?$",
      +  "type": "string"
      +}
    • addedInput schema / properties / keywords / maxItems
      Added value: +20
    • addedInput schema / properties / keywords / minItems
      Added value: +1
    • addedInput schema / properties / keywords / uniqueItems
      Added value: +true
  2. Changed1 schema field changed
    • removedInput schema / properties / granularity
      Removed value: -{
      -  "const": "week",
      -  "default": "week",
      -  "description": "Time granularity. Keyword detail currently supports `week` only.",
      -  "title": "granularity",
      -  "type": "string"
      -}
  3. Changed3 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"
      -]
  4. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Lookup date in YYYY-MM-DD format. Data is stored as weekly snapshots, and the response returns the latest snapshot on or before this date."New value: +"Lookup date in YYYY-MM-DD format. Returns the latest weekly snapshot on or before this date."
  5. Added

TDQS

A4.2/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 and does well: it discloses per-item credit cost (one credit per marketProfile, zero for identity-only), balance prechecking, meta.creditsConsumedExact, context.resolvedDate semantics, and that zero is a measured value. It omits auth/permission requirements and failure behavior, but the billing and data-semantics disclosure is far beyond a bare description.

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?

Front-loaded correctly with the action, and the numbered sections aid scanning, but the text is long and repeats itself: keyword-order/identity preservation is stated in both section 1 and section 3, and seasonality is explained twice. This verbosity costs it against a tighter definition.

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 keyword-analytics tool with no annotations, the description covers the returned dimensions, identity-only items, peakPeriods edge cases, resolvedDate and billing adequately, even though the output schema's data payload is untyped. Auth and error handling remain unaddressed, keeping it short of a 5.

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?

Schema coverage is 100%, so the baseline is 3. The description reinforces date semantics ('latest available snapshot on or before date') and keyword-order preservation for data.items[], but these are largely duplicative of what the schema already states; it adds no syntax or format detail the schema lacks.

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 names a specific verb+resource ('Get keyword market profile') and immediately specifies the returned artifact: six graded market dimensions with raw evidence, ad coverage and annual seasonality at a named path. It also explicitly separates itself from sibling tools (trend-profile, detail, trend), so an agent can distinguish it 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Section 2 lists concrete comparison use cases (demand, concentration, organic entry, supply, brands, product benchmarks) and gives explicit routing rules: use trend-profile with windowPeriods for window-specific volatility, detail for additional snapshot metrics, trend for raw weekly history. It also warns that directions are numeric, not a recommendation to enter or avoid a market.

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