SEO
seo: 7 operations.
Also for this capability: API · CLI · MCP · SDKs
seo: 7 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.
| Tool | seo |
| Address | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | POST /v1/seo/audit · POST /v1/seo/backlinks · POST /v1/seo/competitors · POST /v1/seo/ideas · POST /v1/seo/keywords · POST /v1/seo/rankings · GET /v1/seo/rates |
| Product | seo |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
input | object | — | — | — | arguments for the chosen op |
op | string | yes | — | — | — |
tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means MCP does not constrain the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "seo",
"arguments": {
"op": "<op>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one MCP answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
seo dispatches to 7 operations.
| Operation | Route | Product | Summary |
|---|---|---|---|
seoAudit | POST /v1/seo/audit | seo | Fetch one page and report what it gets wrong |
seoBacklink | POST /v1/seo/backlinks | seo | Who links to a target, and how much of it is broken or spam |
seoCompetitor | POST /v1/seo/competitors | seo | The domains that place for the same phrases |
seoIdea | POST /v1/seo/ideas | seo | Grow a seed phrase into the phrases nobody named yet |
seoKeyword | POST /v1/seo/keywords | seo | How often named phrases are searched, and what a click costs |
seoRank | POST /v1/seo/rankings | seo | Every phrase a domain already places for, with its position |
seoRate | GET /v1/seo/rates | seo | What each call on this surface costs, from the vendor's own list |
The same capability over plain HTTP is in the seo API reference, on https://api.hanzo.ai.
All 120 tools · MCP · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 120 tools captured 2026-09-30.