Skip to main content
Glama
Sign In
semrush-mcp

semrush-mcp

by superseoworld
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

semrush_domain_organic_keywords

Retrieve organic keywords for a domain to analyze search performance and uncover ranking opportunities.

Instructions

Get organic keywords for a specific domain

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": {
      "domain": "<domain>"
    },
    "name": "semrush_domain_organic_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to analyze (e.g., "example.com")
databaseNoDatabase to use (e.g., "us", "uk", "ca", etc.)
limitNoMaximum number of keywords to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits such as side effects, authentication requirements, rate limits, or return format. It only implies a read operation without explicit confirmation.

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 a single concise sentence that effectively communicates the tool's purpose. However, it could include more detail without sacrificing brevity, hence 4.

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

Completeness2/5

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

With no output schema and minimal description, the tool lacks context about the return format, pagination, or result structure. For a tool with three parameters and no annotations, the description is incomplete for effective use.

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 description adds no additional meaning beyond what the input schema provides for domain, database, and limit. Baseline score of 3 is appropriate.

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 clearly states the action ('Get') and resource ('organic keywords for a specific domain'). It effectively distinguishes from sibling tools like semrush_domain_paid_keywords and semrush_domain_overview.

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?

No guidance is provided on when to use this tool versus alternatives like semrush_domain_paid_keywords or semrush_keyword_overview. No prerequisites or exclusions are mentioned.

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