Skip to main content
Glama

Visibility Genies

Get subdomains

get_subdomains

Lists a domain's subdomains in one market, most organic traffic first: each subdomain's estimated organic and paid traffic, its organic and paid keyword counts and its keywords in the top 3 and top 10. Estimated price: up to $0.05, one market data request for up to 100 subdomains, billed by the rows returned. The same domain and market saved within 12 hours is read free, and it opens free on Domain Overview's Subdomains tab. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_subdomains"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoThe domain. Defaults to the project's own.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
languageCodeNoLanguage code such as en, es or vi. When left out, the language of the project's default market is used (see list_projects).
locationCodeNoMarket location code, for example 2840 for the United States. When left out, the project's default market is used (shown by list_projects and changed in project settings). A few countries, Iceland (2352) among them, only have Google Ads data: search volume, CPC and trends are available there, but keyword difficulty, search intent and domain analytics are not.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
boughtNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare openWorldHint and readOnlyHint=false; the description goes far beyond them, disclosing estimated cost ($0.05), row-based billing, one-market-per-request scope, a 12-hour free re-read, the workspace spend-limit hold-and-charge behavior, and the pre-purchase refusal with estimate and maximum. This is exactly the behavioral detail needed for a paid call that is not a plain read.

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 purpose and cost are front-loaded before the spend-limit mechanics, so the agent gets the essentials first. The spend-limit paragraph is long and slightly repetitive ('holds at most its estimate plus a margin while it runs and is charged what it bought'), but each sentence carries operational value.

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

Completeness5/5

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

With an output schema covering return values and annotations covering openness, the description fills the remaining gaps: cost, billing granularity, caching, spend limits, and the recovery path after a refusal. Nothing an agent needs to call this correctly, or to explain cost to a user, is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning for approvedMaxCostUsd by explaining it is only used after a refusal and must be user-approved. It also clarifies that domain defaults to the project's own and that market/language default from project settings, though those points largely mirror the schema.

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 gives a specific verb and resource ('Lists a domain's subdomains in one market, most organic traffic first') and enumerates the returned metrics, so the agent knows exactly what it gets. It never names or contrasts a sibling tool such as get_domain_overview, so it falls short of full sibling differentiation.

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?

Usage context is implied rather than stated: it explains the refusal/approval loop and the 12-hour free-cache window, but gives no guidance on when to pick this tool over domain-overview or competitor tools. The when-to-use knowledge is present for the cost workflow but absent for tool selection.

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