Vee3

domains.metrics

Analyze a domain with comprehensive SEO metrics, backlink data, and social signals.

Returns authority metrics (Moz domain/page authority, Ahrefs domain rating, Majestic trust and citation flow), backlink profile counts (total backlinks, referring domains, EDU/GOV links), traffic and keyword estimates (organic traffic, traffic value, organic keywords, Ahrefs rank), social signals (Facebook shares/comments, Pinterest pins, StumbleUpon), and technical data (IP addresses, subnets, topical trust flow categories).

Cost = 40 tokens.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	Domain name to analyze (for example example.com).

Output Schema

TableJSON Schema

Name	Required	Description
`mozDA`	No	Moz domain authority score (0-100).
`mozPA`	No	Moz page authority score (0-100).
`domain`	No	Analyzed domain name.
`ahrefsDR`	No	Ahrefs domain rating (0-100).
`stumbles`	No	Total StumbleUpon shares.
`FB_shares`	No	Total Facebook shares.
`ahrefsRank`	No	Global website ranking from Ahrefs.
`majesticCF`	No	Majestic citation flow score (0-100).
`majesticTF`	No	Majestic trust flow score (0-100).
`FB_comments`	No	Total Facebook comments.
`last_updated`	No	When the metrics snapshot was last updated.
`ahrefsTraffic`	No	Estimated monthly organic traffic.
`majesticLinks`	No	Total links from the Majestic database.
`pinterest_pins`	No	Total Pinterest saves.
`ahrefsBacklinks`	No	Total number of backlinks from Ahrefs.
`ahrefsRefDomains`	No	Number of unique referring domains from Ahrefs.
`ahrefsTrafficValue`	No	Estimated value of organic traffic.
`ahrefsOrganicKeywords`	No	Number of ranking organic keywords.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJun 22, 2026

changedOutput schema / properties / ahrefsTraffic / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / ahrefsTrafficValue / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

First observedJun 18, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It thoroughly discloses what will be returned (authority metrics, backlink counts, traffic estimates, social signals, technical data) and the token cost. It does not mention potential limitations or explicitly state read-only behavior, but the returns-focused language strongly implies a safe analysis operation.

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 text is front-loaded with the core purpose, followed by a structured, detailed list of return categories and a cost note. There is no redundant or filler content.

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?

For a single-parameter read tool with an output schema, the description provides substantial context: purpose, detailed return categories, and cost. It could be improved by naming alternatives or exclusion cases, but it is otherwise complete.

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 only parameter, domain, is fully described in the schema with an example. The tool description adds no additional parameter semantics beyond the schema's 100% coverage, so the baseline score of 3 applies.

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 opens with a specific action ('Analyze a domain') and enumerates the exact data categories (SEO metrics, backlinks, social signals), clearly distinguishing it from sibling domain tools like domains.whois or domains.dns_records.

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?

It implies use when a broad domain analysis is needed, but does not explicitly contrast with alternative tools (e.g., seo.url_metrics or domains.whois) or state exclusions. The 'comprehensive' framing provides context but no direct when/when-not guidance.

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

All Vee3 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.