Ubersuggest MCP Server

ubersuggest_traffic_estimation

Estimate organic traffic potential for a domain within a specified time period using integration with Ubersuggest SEO platform for AI-assisted SEO analysis.

Instructions

Estimate organic traffic potential for a 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": "ubersuggest_traffic_estimation"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain to analyze
`period`	No	Time period for analysis

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 15, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states the tool estimates traffic potential but doesn't cover aspects like data sources, accuracy, rate limits, authentication needs, or what the output might look like. This is a significant gap for a tool with no structured behavioral hints.

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?

The description is a single, efficient sentence that front-loads the core purpose without any wasted words. It's appropriately sized for a tool with two parameters and no complex behavioral nuances to explain.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the estimation returns, how it's calculated, or any prerequisites, making it inadequate for an agent to fully understand the tool's behavior and output in context.

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?

The schema description coverage is 100%, so the schema already documents both parameters ('domain' and 'period') adequately. The description adds no additional meaning beyond what the schema provides, such as examples or constraints, but doesn't need to compensate for low coverage. This meets the baseline for high schema coverage.

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 clearly states the tool's purpose with a specific verb ('Estimate') and resource ('organic traffic potential for a domain'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'ubersuggest_domain_overview' or 'ubersuggest_keyword_research', which might also involve traffic analysis, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools or contexts where this estimation is preferred over other analyses, leaving the agent to infer usage based on tool names alone.

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

Deploy Server