Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

Lexical keyword grouping

seo-content_keyword-group-lexical
Read-onlyIdempotent

Group keywords that share the same Porter2 stem signature, optionally merging groups by SERP URL overlap. Price $0.03 USDC. POST /api/v1/seo-content/keyword-group-lexical. 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-group-lexical"
  }
}

Input Schema

NameRequiredDescriptionDefault
serpsNoserps, value. Optional.
keywordsYeskeywords, array. Required.
maxGroupSizeNomaxGroupSize, integer, from 1 to 5000. Required.
minSharedUrlsNominSharedUrls, integer, from 1 to 10. Required.

Output Schema

NameRequiredDescriptionDefault
groupsNogroups. Array.
sourcesNosources. Array.
ungroupedNoungrouped. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful operational context the annotations cannot express: a concrete price ($0.03 USDC), the HTTP endpoint, and the x402 failure mode where an unpaid call returns payment terms and performs no work. It does not cover limits or output shape, but with an output schema present that is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler: the core behavior is front-loaded first, then the cost, then the endpoint and payment failure mode. Every sentence carries information an agent needs before calling.

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 read-only grouping tool with an output schema (so return values need not be described), the definition covers purpose, method, cost, and the non-execution path for unpaid calls. The only shortfall is that maxGroupSize and minSharedUrls behavior is left entirely to their schema defaults, which matters for how groups are split.

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 adds real meaning the schema's placeholder-style parameter docs ("serps, value. Optional.") do not: keywords are grouped by stem signature and serps drives the optional URL-overlap merge. Neither maxGroupSize nor minSharedUrls is explained in the description, so it does not fully clear the baseline-plus bar.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Group keywords") plus the discriminating mechanism: groups share a Porter2 stem signature, with optional merging by SERP URL overlap. That distinguishes it from neighboring analysis tools like near-duplicate-detect or tfidf-term-gap. It stops short of explicitly naming a sibling it should be preferred over, so a 4 rather than 5.

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?

The phrase "optionally merging groups by SERP URL overlap" implies when to supply SERP data, and the payment sentence clarifies what happens on an unpaid call. However, there is no explicit statement of when to choose this tool over the other keyword tools in the catalog, so guidance is implied rather than stated.

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