AIsa SEO & AI Visibility

Ahrefs Site Metrics

get_ahrefs_site_metrics

Read-onlyIdempotent

Return core Site Explorer metrics for a target domain on a given date: organic and paid keyword counts, top-3 keyword count, organic traffic, and traffic value. 4xx/5xx are not charged.

Published reference price: $0.08 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

Name	Required	Description	Default
`date`	Yes	Snapshot date in `YYYY-MM-DD` format.
`target`	Yes	Target domain, e.g. `ahrefs.com`.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026
- addedInput schema / properties / target / example
```
Added value: +"ahrefs.com"
```
- changedInput schema / required
```
Previous value: -[
-  "target",
-  "date"
-]New value: +[
+  "date",
+  "target"
+]
```
Changed2 schema fields changedOct 15, 2026
- removedInput schema / properties / target / example
```
Removed value: -"ahrefs.com"
```
- changedInput schema / required
```
Previous value: -[
-  "date",
-  "target"
-]New value: +[
+  "target",
+  "date"
+]
```
Changed2 schema fields changedOct 15, 2026
- addedInput schema / properties / target / example
```
Added value: +"ahrefs.com"
```
- changedInput schema / required
```
Previous value: -[
-  "target",
-  "date"
-]New value: +[
+  "date",
+  "target"
+]
```
First observedSep 15, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds non-obvious billing behavior ('4xx/5xx are not charged') and the $0.08 per successful request cost, which are genuine operational facts the agent cannot get from structured fields.

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 core sentence is front-loaded and dense with real content, and the error-charging note is short. The delimited aisa-pricing boilerplate is standardized noise rather than authored prose, though it does consume space for a single price figure.

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?

An output schema exists, so return-value structure need not be explained, and both required parameters are fully documented. For a simple two-parameter read tool this is nearly complete; only the lack of any routing context versus the competing Semrush/DataForSEO domain tools leaves a gap.

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 description coverage is 100% (date format/example and target domain example are documented in the schema), so the baseline is 3. The description only restates 'target domain' and 'a given date' without adding format, normalization, or subdomain/path handling detail.

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?

Specific verb ('Return') plus precise resource ('core Site Explorer metrics for a target domain on a given date'), and the enumerated metric list (organic/paid keyword counts, top-3 count, organic traffic, traffic value) differentiates it from near siblings like get_ahrefs_domain_rating and get_semrush_domain_overview.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative-tool guidance. Given the many Semrush and DataForSEO domain-metric siblings, the agent gets no help deciding between this and get_semrush_domain_overview; only the metric list implicitly suggests a domain-level overview use case.

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

All AIsa SEO & AI Visibility 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?