Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

Transparent keyword difficulty

seo-content_keyword-difficulty-estimate
Read-onlyIdempotent

Estimate keyword difficulty as 100 × mean of capped log referring-domain scores from the caller-supplied top results. Price $0.02 USDC. POST /api/v1/seo-content/keyword-difficulty-estimate. 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": {
      "keyword": "<keyword>",
      "results": "<results>"
    },
    "name": "seo-content_keyword-difficulty-estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYeskeyword, string, length 1 to 500. Required.
resultsYesresults, array. Required.
referenceCapNoreferenceCap, integer, from 1 to 9007199254740991. Required.
serpFeaturesNoserpFeatures, array. Required.

Output Schema

NameRequiredDescriptionDefault
formulaNoformula. String.
sourcesNosources. Array.
coverageNocoverage. Number.
componentsNocomponents. Array.
difficultyNodifficulty. Number.
limitationsNolimitations. Array.
lowConfidenceNolowConfidence. Boolean.
difficultyExactNodifficultyExact. Number.
serpFeatureCountNoserpFeatureCount. Number.

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 read-only, idempotent, non-destructive, and open-world behavior, so the bar is lower, yet the description adds real value beyond them: the $0.02 USDC price and the key operational quirk that an unpaid call returns x402 payment terms and does not execute. The algorithm formula also reveals the tool is a pure, reproducible computation. It does not mention handling of null referringDomains or empty result sets.

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?

Four short sentences, front-loaded with the definition, then price, endpoint, and the unpaid-call gotcha. Every sentence carries information an agent needs to call this correctly; nothing is redundant.

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 present, return values need not be described, and the description covers the computation, cost, endpoint, and payment failure mode. Remaining gaps are minor edge cases (empty results, null referringDomains, how serpFeatures affects the score).

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 parameter documentation is already handled structurally and the baseline of 3 applies. The description adds only indirect meaning — 'caller-supplied top results' maps to the results array and 'capped' hints at referenceCap — and says nothing about serpFeatures.

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?

States a specific verb and resource ('Estimate keyword difficulty') and even the exact computation ('100 × mean of capped log referring-domain scores'), which tells the agent this is a deterministic calculation over caller-supplied data rather than a SERP fetch. It does not explicitly contrast itself with siblings like keyword-opportunity-score, so it falls just short of a 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?

Usage is implied rather than stated: the agent learns it must already hold top SERP results ('caller-supplied top results'), which scopes when the tool applies. Beyond that there is no explicit when-to-use/when-not-to-use guidance or named alternative for fetching SERP data.

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