Skip to main content
Glama

Seo Keywords Ads

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 })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": [
        "running shoes",
        "trail shoes",
        "athletic footwear"
      ]
    },
    "name": "seo_keyword_google_ads_volume"
  }
}

Input 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
    • changedInput schema / examples
      Previous 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
      -  }
      -]New value: +[
      +  {
      +    "keywords": [
      +      "running shoes",
      +      "trail shoes",
      +      "athletic footwear"
      +    ]
      +  },
      +  {
      +    "keywords": [
      +      "digital marketing agency"
      +    ],
      +    "language_code": "en",
      +    "location_code": 2840
      +  }
      +]
  2. 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
      +  }
      +]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds genuine behavioral context the annotations do not: the numbers come from Google's own Ads API, are monthly, and include competition and CPC; the "cheaper" remark also hints at cost trade-offs versus the sibling. It stops short of stating rate limits or quota behavior, which keeps it from a 5.

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?

Front-loaded with the core capability, then routing guidance, then a concrete call example; every sentence earns its place and there is no filler. The backticked placeholder and example are compact rather than redundant.

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?

No output schema exists, but the description names the returned fields (monthly volume, competition, CPC) and the source, so the agent knows what to expect. Combined with full schema coverage and rich annotations, nothing material is missing for correct invocation.

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 schema already documents keywords (max 10), language_code, location_code, and _apiKey. The description only reinforces the max-10 limit and demonstrates location_code via the example; it adds little semantic meaning the schema does not already carry, so baseline 3 applies.

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?

States a specific verb+resource (exact Google Ads search volume per keyword), the data source (Ads API), and what is returned (volume, competition, CPC). It explicitly contrasts itself with seo_keyword_overview, so an agent can distinguish the two without opening either schema.

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?

Gives an explicit when-to-use condition ("when you specifically need Google Ads figures") and names the alternative (seo_keyword_overview) with a reason to prefer it (cheaper, adds keyword difficulty). This is precise routing guidance rather than implied usage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.