Vee3

seo.keyword_metrics

Get SEO metrics for a search keyword in a specific country market.

Returns keyword, searchVolume, clicks, cpc, difficulty, globalSearchVolume, and trafficPotential.

Cost = 10 tokens.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`country`	No	2-letter ISO country code for the target market (default us). Use seo.country_codes for supported values.	us
`keyword`	Yes	Search keyword or phrase to analyze.

Output Schema

TableJSON Schema

Name	Required	Description
`cpc`	No	Estimated cost per click in paid search.
`clicks`	No	Estimated monthly clicks from organic search.
`keyword`	No	Analyzed keyword.
`difficulty`	No	Keyword difficulty score (higher is harder to rank).
`searchVolume`	No	Estimated monthly search volume in the selected country.
`trafficPotential`	No	Estimated traffic potential if ranking well.
`globalSearchVolume`	No	Estimated global monthly search volume.

Schema Changelog

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

Changed1 schema field changedJul 3, 2026

changedOutput schema / properties / cpc / anyOf

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

First observedJun 18, 2026

TDQS

A4/5.0

Behavior3/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 adds cost (10 tokens) and lists return fields, but does not explicitly state that the operation is read-only or mention any side effects, rate limits, or error conditions. It provides some transparency but leaves room for more.

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 three short sentences: purpose, return fields, and cost. Every sentence adds value, and the most important information is front-loaded. No filler or redundancy.

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 simple two-parameter tool with an output schema, the description covers the essential context: what it does, what it returns, and its cost. The schema already documents country code guidance via seo.country_codes. It is complete for practical selection and invocation, though it could mention any rate limits or the read-only nature explicitly.

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%, so the baseline is 3. The description reinforces that the tool analyzes a keyword in a country market, matching the schema's parameter descriptions. However, it adds no extra detail beyond what the schema already provides.

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 uses a specific verb ('Get') and resource ('SEO metrics for a search keyword') and explicitly scopes to 'a specific country market'. This clearly distinguishes it from sibling tools like seo.url_metrics (URL metrics) and seo.basic_metrics.

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?

The description clearly states the use case: obtaining SEO metrics for a keyword in a country market. It implies when to use it but does not explicitly mention alternatives or when not to use it. The context is unambiguous, but exclusions are absent.

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.