Vee3

google-search.url_traffic_insights

Get Google keyword traffic insights and related keyword suggestions for a URL.

Returns an array of keyword suggestions. Each item includes text, monthly search volume, competition_level, competition_index, low_bid, high_bid, and trend.

Required: url and language (for example en). Optional: location (for example US) for country-specific data; omit location for global results (default). Optional: min_search_volume (default 0) and intent (informational, navigational, commercial, or transactional).

Cost = 20 tokens.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Public http or https URL to get traffic insights and suggestions for.
`intent`	No	Filter by search intent: informational, navigational, commercial, or transactional.
`language`	Yes	Language code for the search market (for example en).
`location`	No	Optional country or region code for localized traffic (for example US). Omit for global URL keyword insights.
`min_search_volume`	No	Minimum monthly search volume; only keywords at or above this threshold are returned.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`keyword_suggestions`	No	Keyword suggestions with traffic and competition metrics.

Schema Changelog

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

Changed3 schema fields changedJul 3, 2026

changedOutput schema / $defs / SeoUrlTrafficInsightsResponseKeywordSuggestionsItem / properties / high_bid / anyOf

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

changedOutput schema / $defs / SeoUrlTrafficInsightsResponseKeywordSuggestionsItem / properties / low_bid / anyOf

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

changedOutput schema / $defs / SeoUrlTrafficInsightsResponseKeywordSuggestionsItem / properties / trend / anyOf

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

First observedJun 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are present, so the description carries the burden. It discloses the return structure (array of keyword suggestions with fields), token cost, and parameter defaults. It omits failure modes/rate limits, but for a read-only insights tool this is adequate.

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?

Four short, information-dense sentences; front-loaded with purpose, then output, then parameters, then cost. No filler.

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

Completeness5/5

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

With a comprehensive input schema and output schema, the description still adds valuable context: cost, default behavior for location, and output fields. Ample for the tool's complexity.

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%, so baseline 3. The description restates parameter requirements and adds language/country examples, but no new semantic info beyond the schema.

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?

Description opens with 'Get Google keyword traffic insights and related keyword suggestions for a URL' – a specific verb and resource. It clearly distinguishes from sibling `google-search.keyword_traffic_insights` by anchoring on URL.

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?

Explicitly lists required parameters (url, language) and optional ones (location, min_search_volume, intent) with examples. It does not name sibling alternatives, but the URL-anchored purpose makes the use case clear.

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.