Vee3

google-search.keyword_traffic_insights

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

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

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

Cost = 20 tokens.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Keyword suggestion filter: exact returns only suggestions that exactly match the seed keyword; all returns all suggestions (default).	all
`intent`	No	Filter by search intent: informational, navigational, commercial, or transactional.
`keyword`	Yes	Seed keyword to get traffic insights and suggestions for.
`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 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 / SeoKeywordTrafficInsightsResponseKeywordSuggestionsItem / properties / high_bid / anyOf

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

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

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

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

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

First observedJun 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description bears the full burden. It discloses the return array structure with field names, notes the token cost, and explains default modes and location behavior. It doesn't discuss error handling or rate limits, but for a read-only 'Get' tool this is sufficient.

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 compact and well-organized: purpose sentence, return-format sentence, parameter requirements, and cost. Every sentence adds useful information without 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?

With an output schema present, the description doesn't need to fully enumerate return fields, but it still summarizes them. It covers the essential operational aspects: required parameters, optional filters, and cost. It could add more about response size or errors, but overall it's appropriately comprehensive.

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 the schema already fully documents all six parameters. The description summarizes required and optional parameters but adds little beyond the schema—it repeats defaults already in the schema, such as location's default global behavior and mode's default 'all'.

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 first sentence clearly identifies the resource (Google keyword traffic insights) and the specific verb (Get), with 'for a seed keyword' clarifying the scope. It distinguishes from sibling url_traffic_insights by focusing on keyword-based search rather than URL-based.

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 provides clear context on required vs optional parameters and gives examples (language 'en', location 'US') and explains the default behavior for location omission. However, it doesn't explicitly name alternatives or state when not to use this tool relative to siblings like url_traffic_insights.

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.