Mark

Analyze Domain

analyze_domain

Looks up any domain (yours or a competitor's): view = overview | top_pages | page_keywords | backlinks. overview, top_pages and page_keywords fetch fresh data from the provider, 1 domain per call. For backlinks, refresh: true fetches a fresh snapshot; otherwise it returns the latest one. Each call spends provider calls, except backlinks without refresh, which reads the stored snapshot. Related: research_keywords, get_rankings.

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>",
      "view": "<view>"
    },
    "name": "analyze_domain"
  }
}

Input Schema

Name	Required	Description
`url`	No	Required for page_keywords: the page URL.
`view`	Yes	Which cut of the domain to return.
`domain`	Yes	example.com or a full URL.
`siteId`	No	Workspace site id for the backlinks view.
`refresh`	No	For backlinks, fetch a fresh snapshot.
`languageCode`	No	Language code. Defaults to the priority market.
`locationCode`	No	DataForSEO location. Defaults to the priority market.

Output Schema

Name	Required	Description	Default
`view`	Yes
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / refresh / description

Previous value: -"For backlinks, fetch a fresh paid snapshot."New value: +"For backlinks, fetch a fresh snapshot."

First observedOct 1, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the cost model (each call spends provider calls, except cached backlinks) and the freshness/caching semantics per view. These are the exact traits an agent needs to avoid burning quota or unintentionally returning stale data, none of which appear in readOnlyHint/openWorldHint/idempotentHint.

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?

Dense but front-loaded: the view enumeration and scope come first, then freshness and cost semantics. Every sentence carries information, though the freshness and cost statements could be tightened into one clause without loss.

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 describe return shapes, and it covers scope, views, freshness, and cost well for a 7-parameter tool. The only gap is the lack of explicit sibling routing for keyword/ranking lookups, which is the most likely source of mis-selection in this large sibling set.

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; the description lifts this by explaining cross-parameter conditionality — that refresh only matters for backlinks and that backlinks otherwise returns a stored snapshot, and that the other views always fetch fresh. It reinforces but doesn't fully restate the url/page_keywords dependency already documented in 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?

States a specific verb (looks up) and resource (any domain, yours or a competitor's) and enumerates the four view cuts, so an agent knows exactly what capability it gets. It names related siblings (research_keywords, get_rankings) but doesn't say what distinguishes this tool from them, leaving the boundary fuzzy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete operational guidance: one domain per call, refresh only applies to the backlinks view, and non-refresh backlinks reads the stored snapshot. It doesn't route the agent between this tool and research_keywords/get_rankings, listing them only under 'Related' rather than stating which to pick when.

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

All Mark tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?