seo-keyword-ad-traffic-forecast

Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Initialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.

{
  "jsonrpc": "2.0",
  "id": "seo-keyword-ad-traffic-forecast-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_seo_keyword_ad_traffic_forecast",
    "arguments": {
      "bidUsd": 1,
      "dateFrom": "2026-10-01",
      "dateTo": "2026-10-02",
      "keywords": [
        " Shoes ",
        "BOOTS"
      ]
    }
  }
}

Progress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.

Arguments

Response fields

Treat structuredContent as the programmatic API response payload.

Examples

{
  "bidUsd": 1,
  "dateFrom": "2026-10-01",
  "dateTo": "2026-10-02",
  "keywords": [
    " Shoes ",
    "BOOTS"
  ]
}

{
  "code": 0,
  "cost": "-1",
  "data": {
    "callId": "00000000-0000-4000-8000-000000000001",
    "reason": "IN_PROGRESS",
    "retryable": false,
    "status": "PROCESSING"
  },
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Related MCP tools