Skip to main content
Glama

Vee3

by io.github.Vee3io
OverviewAdmin

seo.url_metrics

Get detailed Ahrefs SEO metrics for a specific URL.

Returns two sections:

  • page: backlinks, referring domains, estimated traffic, traffic value, organic keywords, URL rating, and word count on the page

  • domain: domain rating, rank, backlinks, referring domains, traffic, traffic value, and organic keywords

Cost = 10 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic page URL to analyze.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoMetrics for the requested page URL.
domainNoMetrics for the parent domain.

Schema Changelog

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

  1. Changed4 schema fields changed
    • changedOutput schema / $defs / SeoUrlMetricsResponseDomain / properties / domainRating / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / $defs / SeoUrlMetricsResponseDomain / properties / traffic / anyOf
      Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / $defs / SeoUrlMetricsResponsePage / properties / traffic / anyOf
      Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / $defs / SeoUrlMetricsResponsePage / properties / urlRating / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds a cost note ('Cost = 10 tokens') and describes the output structure transparently, but it doesn't explicitly state that the operation is read-only or has no side effects, though 'Get' implies this.

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 tightly written with no redundant words, uses a clear two-section breakdown, and the cost line is useful. Four sentences deliver high information density without unnecessary detail.

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?

The description covers purpose, output structure, and cost. Given the tool has only one parameter and an output schema exists, this is nearly complete; it omits only explicit usage alternatives and edge cases, but those don't impede initial invocation.

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?

Schema coverage is 100% with the url parameter described as 'Public page URL to analyze.' The description adds little beyond that, merely referring to 'specific URL' without clarifying required format, protocol, or edge cases, so the baseline 3 is appropriate.

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 'Get detailed Ahrefs SEO metrics for a specific URL' and lists the page and domain sections, making the tool's purpose unambiguous. However, it doesn't explicitly contrast with sibling SEO tools like seo.basic_metrics, so it stops short of a full 5.

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 description implies use when you need comprehensive SEO metrics for a URL but doesn't provide explicit guidance on when to choose this over alternatives like seo.basic_metrics or seo.backlinks, nor does it state any exclusions. The usage context is only implied.

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

All Vee3 toolsInspect
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.

Resources