Skip to main content
Glama

Seo Keywords Ads

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Seo Keyword Google Ads Volume

seo_keyword_google_ads_volume
Read-onlyIdempotent

Exact Google Ads search volume for <keyword> — Google's own monthly search-volume numbers (plus competition and CPC) from the Ads API, for up to 10 keywords. Use when you specifically need Google Ads figures; for general SEO volume + keyword difficulty, prefer seo_keyword_overview (cheaper). Example: seo_keyword_google_ads_volume({ keywords: ["running shoes"], location_code: 2840, _apiKey: "your-base64-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesDataForSEO API key = base64("login:password") from your dataforseo.com account
keywordsYesKeywords to look up (max 10), e.g. ["running shoes", "trail shoes"]
language_codeNoTwo-letter language code (default "en")
location_codeNoDataForSEO location code (default 2840 = United States)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-seo-keywords-ads-api-key",
+    "keywords": [
+      "running shoes",
+      "trail shoes",
+      "athletic footwear"
+    ]
+  },
+  {
+    "_apiKey": "your-seo-keywords-ads-api-key",
+    "keywords": [
+      "digital marketing agency"
+    ],
+    "language_code": "en",
+    "location_code": 2840
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and no destructiveness. Description adds context: data source (Ads API), limit of 10 keywords, and return fields (volume, competition, CPC). No contradictions.

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?

Three sentences, includes a concrete example call, front-loaded with the return value. Every sentence adds essential information without redundancy.

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?

Despite no output schema, description adequately explains return values (volume, competition, CPC). Differentiates from sibling tool, covers limits, and provides example. Annotations and schema are rich, making the description complete.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the _apiKey format (base64 of login:password), clarifying the max 10 keywords, and providing example usage with defaults.

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 specifies it returns 'Exact Google Ads search volume' with competition and CPC from the Ads API, clearly distinguishing it from the sibling tool seo_keyword_overview.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('when you specifically need Google Ads figures') and when to prefer an alternative (seo_keyword_overview for general SEO volume), including a cost hint.

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

All Seo Keywords Ads toolsInspect
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