Skip to main content
Glama

Look up a domain

lookup_domain

Organic keywords, estimated traffic, and top ranking URLs for a domain. Costs 10¢ from the user's BudgetSEO balance unless the result is already cached. Tell the user the cost and wait for a yes. countryCode defaults to US.

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": "lookup_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
countryCodeNoTwo-letter country code. Defaults to US.

Output Schema

NameRequiredDescriptionDefault
top3Yes
top10Yes
domainYes
movementYes
fromCacheYes
countryCodeYes
creditsSpentYes
rankedKeywordsYes
organicKeywordsYes
estimatedTrafficYes
estimatedTrafficValueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description adds genuinely non-derivable behavior — a 10¢ charge against the user's BudgetSEO balance, a cache that avoids the charge, and a mandatory user confirmation step. It stops short of stating what happens on a failed or empty lookup (whether the charge still applies) or how fresh the cached data is.

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?

Three short sentences, each carrying a distinct load: what you get, what it costs, and how to get consent. The cost and consent constraint is front-loaded appropriately for a paid call, and there is no filler.

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, the description needn't explain return shape, and for a two-parameter paid read it covers the essentials an agent needs: cost, cache, confirmation, and the country default. The remaining gap is the accepted domain format and charge-on-failure behavior, which matter for correct invocation in edge cases.

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?

Only half the parameters carry schema descriptions, and the description compensates barely at all: it merely restates that countryCode defaults to US, duplicating the schema text. The critical ambiguity for 'domain' — whether a bare root domain, a full URL, or a subdomain is accepted (the schema only sets minLength 3) — is left entirely unaddressed.

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 the concrete deliverables — organic keywords, estimated traffic, top ranking URLs — for a domain, which goes well beyond the bare name 'lookup_domain'. It does not explicitly differentiate from siblings like lookup_keywords or get_competitor_overview, so the agent must infer that this is the broad domain-level overview rather than a keyword-specific lookup.

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?

The workflow guidance is strong where it exists: 'Tell the user the cost and wait for a yes' tells the agent exactly what to do before invoking. However, there is no statement of when to choose this tool versus lookup_keywords, lookup_backlinks, or get_competitor_overview, so tool selection among the siblings is left implicit.

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