Skip to main content
Glama
newilu

ahrefs-mcp

by newilu

Site metrics by country

site-metrics-by-country

View organic traffic distribution by country for any domain. Identify the real geographic audience of a website to tailor SEO strategies.

Instructions

Organic traffic of a domain split by country. Shows the site's real geography.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
targetYesDomain or URL to analyze, e.g. example.com
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the output is by country but does not disclose limitations (e.g., only organic traffic), data freshness, or how country geography is determined. The 'real geography' phrase is vague and lacks concrete behavioral detail.

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 description is two short sentences and is concise, but the second sentence ('Shows the site's real geography') adds little concrete information and is somewhat redundant with the first sentence.

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

Completeness3/5

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

For a simple read tool with two parameters and no output schema, the description conveys the core function. However, the lack of parameter documentation and any note about response format leaves gaps, making it only minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% (target is described, limit is not). The description does not mention either parameter, failing to compensate for the undocumented 'limit' parameter or add any meaning beyond 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 clearly states the tool provides organic traffic of a domain split by country, which distinguishes it from site-metrics (overall metrics) and keyword-volume-by-country (keyword-level data). The verb is implied rather than explicit, but the resource and scope are specific.

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?

No guidance is given on when to use this tool versus siblings such as site-metrics or keyword-volume-by-country. The only context is implied by the tool name and description, with no exclusions or alternatives mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/newilu/ahrefs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server