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

keyword-steroids-gold

by MaximKonovalovDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gold_keyword_brief

Generate a one-page content brief from a seed keyword: H1/title/meta formulas, H2 outline from autocomplete clusters, word-count band by intent, and internal-link anchors.

Instructions

POWER: one-page content brief from a seed keyword - H1/title/meta formulas, H2 outline skeleton from autocomplete clusters, word-count band by intent, internal-link anchors list. Uses the free suggest engine. PAID ONLY $29.

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": {
      "seed": "<seed>"
    },
    "name": "gold_keyword_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
seedYes
regionNous

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses the data source ('free suggest engine'), the cost constraint ('PAID ONLY $29'), and the generated output structure. It does not mention rate limits or explicitly confirm read-only behavior, but the framing makes the main behavior clear.

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 two sentences and front-loads the core deliverable before adding cost/source context. The 'POWER:' prefix is promotional noise, but the rest is economical and avoids unnecessary repetition.

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 tool with only one required parameter, the description provides enough context for an agent to understand what the tool does and decide to call it. Minor gaps include the lack of detail on how lang/region influence output and no mention of return format, but these are secondary for selection.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to compensate. It clarifies the meaning of 'seed' ('seed keyword') but gives no semantics for 'lang' or 'region', such as accepted formats, possible values, or how they affect the suggest engine.

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 states a concrete deliverable ('one-page content brief') built from a 'seed keyword' and lists the exact sections included (H1/title/meta formulas, H2 outline, word-count band, internal-link anchors). This clearly differentiates it from sibling tools like gold_keyword_expand, which is about expanding keywords rather than producing a brief.

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?

When to use it is implied: call it when you need a content brief from a seed keyword. However, it does not explicitly name alternatives or state when to prefer siblings such as gold_keyword_expand or gold_cluster, so the agent must infer routing from the output description.

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