Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

Rule-based keyword intent labels

seo-content_keyword-intent-classify
Read-onlyIdempotent

Label keywords as navigational, transactional, commercial or informational from bundled English modifier rules and caller brands. Price $0.02 USDC. POST /api/v1/seo-content/keyword-intent-classify. An unpaid call returns the x402 payment terms and does not run.

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": "seo-content_keyword-intent-classify"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandsNobrands, array. Required.
keywordsYeskeywords, array. Required.
languageNolanguage, string. Required.en

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive behavior, so the description does not need to restate safety. It does add genuinely non-obvious behavior: a $0.02 USDC charge and the x402 flow where an unpaid call returns payment terms and does not run — a critical precondition an agent would otherwise miss. What is still absent is how deterministic or how coarse the rule-based labels are, but the incremental value is real.

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?

Three short sentences, front-loaded with purpose, then price, then endpoint and payment behavior. Every sentence carries an operational fact; the raw route string is the least essential element but is harmless boilerplate.

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?

With an output schema and full annotation coverage, the description only needs to fill behavioral gaps, and it does: cost and the x402 unpaid-call condition are disclosed. The remaining gap is the tension between an English-only rule set and an exposed 'language' parameter, which is left unexplained.

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 description coverage is 100%, so the baseline is 3. The only added semantics is the phrase 'caller brands', which implies brand terms feed navigational labeling — a modest hint beyond the schema's generic 'brands, array'. The description says nothing about the 'language' parameter even though the stated rules are English-only, which could mislead a caller passing another language.

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 and resource (label keywords) plus the exact output label set (navigational, transactional, commercial, informational) and the mechanism (bundled English modifier rules plus caller brands). No sibling in the catalog does intent classification, so it is distinguishable on the face of the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool to call when it needs intent buckets on a keyword list. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling for a related job (e.g., difficulty or grouping). The 'rule-based/English' framing hints at limitations but is not framed as guidance.

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