Skip to main content
Glama
Sign In

SEO and Keyword Data API

by com.duoleads.keywords
OverviewDiscussionsAdmin

Search intent (up to 100 keywords)

search_intent
Read-onlyIdempotent

Search intent of up to 100 keywords in one $0.04 call: the main intent (informational, navigational, commercial or transactional) with its probability, plus secondary intents. Use when you need to map keywords to funnel stage or content type. Any language; no location needed. Over 100 keywords is a free 400. Keywords not classified are listed in missing (still charged). Bad input is free; upstream errors are not charged. Price: $0.04 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": "<keywords>"
    },
    "name": "search_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesKeywords to classify (1-100; each at most 80 characters, normalised to lower case; one that is then empty, over 10 words or over 80 characters is listed in missing).
languageCodeNoAccepted for compatibility and ignored: the classifier detects the language itself.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark this read-only, idempotent and open-world, and the description goes well beyond them: per-call price, x402/USDC payment mechanics via _meta['x402/payment'], free 400 on oversize batches, partial-failure semantics (unclassified keywords appear in 'missing' and are still charged), and the bad-input-vs-upstream-error billing distinction. That is exactly the billing and failure context annotations cannot convey.

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?

Front-loaded with capability and output shape, then constraints, then billing. Dense but almost every clause carries information; the payment-protocol sentence is necessary for invocation but is the heaviest part of an otherwise tight paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still defines the return shape (main intent, probability, secondary intents, missing list) and covers cost, failure modes and language handling. An agent has everything needed to invoke it correctly and predict the result.

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 both parameters are already documented in-schema, including the languageCode-ignored note and the 1-100 / 80-character normalisation rules. The description only restates the 100-keyword cap and 'any language; no location needed', which is baseline-level reinforcement rather than new meaning.

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 specific verb and resource ('Search intent of up to 100 keywords') and enumerates the exact output taxonomy (informational, navigational, commercial, transactional) with probability plus secondary intents. That distinguishes it cleanly from the many volume/difficulty siblings such as keyword_search_volume and keyword_difficulty without the agent 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 Guidelines4/5

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

Gives a concrete trigger: 'Use when you need to map keywords to funnel stage or content type', plus boundary conditions (any language, no location needed, >100 keywords is a free 400). It stops short of naming a sibling alternative or stating when-not-to-use, so it is clear context rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SEO and Keyword Data API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources