Skip to main content
Glama
Sign In
keyword-steroids-gold

keyword-steroids-gold

by MaximKonovalovDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gold_keyword_gap_scan

Scan up to 100 Hebrew queries for Israel to find keyword gaps where 0-1 shops rank, highlighting open SEO opportunities.

Instructions

Bulk gap scan — 100 queries x region=il lang=he bsearch heuristic. Flags 0-1 shops = OPEN. PAID ONLY PRO $29. No free tier.

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": {
      "queries": "<queries>"
    },
    "name": "gold_keyword_gap_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
glNoil
langNoiw
queriesYesup to 100 Hebrew queries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly discloses that the tool is PAID ONLY PRO $29 with no free tier, that it uses a 'bsearch heuristic,' and that it flags results with 0-1 shops as OPEN. This is meaningful behavioral information, though it omits auth, error, and response-structure detail.

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?

The description is compact and front-loaded with the core action, followed by scope, output semantics, and pricing. Every fragment provides useful signal. It is telegraphic rather than fully structured, but the conciseness is effective.

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

Completeness3/5

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

The description captures essential operational constraints and output meaning, and the lack of annotations means it must cover a lot. However, it does not explain prerequisites, return format, authentication, or when to use this versus siblings like gold_semrush_gap, so an agent still faces meaningful ambiguity in real invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, so the description must compensate. It maps 'region=il' to the gl parameter, 'lang=he' to the lang parameter, and '100 queries' to the queries limit, adding semantics the schema does not fully provide. The 'lang=he' vs schema default 'lang=iw' is a minor ambiguity, but the intent is clear.

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 names a concrete operation, 'Bulk gap scan', and adds operational detail: 100 queries, region=il, lang=he, bsearch heuristic, and the output meaning 'Flags 0-1 shops = OPEN.' This makes the tool's function reasonably clear, though it does not explicitly differentiate it from the sibling gold_semrush_gap.

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

Usage Guidelines2/5

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

There is no guidance about when to choose this tool over alternatives such as gold_semrush_gap or the other keyword tools. The description implies bulk Hebrew/Israel usage but never states conditions, exclusions, or prerequisites, so an agent is left to infer the right selection context.

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

Deploy Server

Other Tools