Skip to main content
Glama

Seo Keyword Overview

seo_keyword_overview
Read-onlyIdempotent

Monthly search volume & difficulty for <keyword>, returns Google search volume, keyword difficulty (0-100), CPC, and competition for up to 10 keywords at once. Keyword research for SEO. Example: seo_keyword_overview({ keywords: ["running shoes", "trail 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"
      ],
      "language_code": "en",
      "location_code": 2840
    },
    "name": "seo_keyword_overview"
  }
}

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-api-key",
      -    "keywords": [
      -      "running shoes",
      -      "trail shoes"
      -    ],
      -    "language_code": "en",
      -    "location_code": 2840
      -  },
      -  {
      -    "_apiKey": "your-seo-keywords-api-key",
      -    "keywords": [
      -      "best gaming laptop",
      -      "laptop for developers"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "keywords": [
      +      "running shoes",
      +      "trail shoes"
      +    ],
      +    "language_code": "en",
      +    "location_code": 2840
      +  },
      +  {
      +    "keywords": [
      +      "best gaming laptop",
      +      "laptop for developers"
      +    ]
      +  }
      +]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "_apiKey": "your-seo-keywords-api-key",
      +    "keywords": [
      +      "running shoes",
      +      "trail shoes"
      +    ],
      +    "language_code": "en",
      +    "location_code": 2840
      +  },
      +  {
      +    "_apiKey": "your-seo-keywords-api-key",
      +    "keywords": [
      +      "best gaming laptop",
      +      "laptop for developers"
      +    ]
      +  }
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the bar is lower; the description still adds valuable behavioral content by enumerating the returned metrics and the max-10-keywords cap, which matters because there is no output schema. It omits cost/credit consumption and rate-limit behavior typical of this kind of paid data API.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The return information and batch limit are front-loaded in the first sentence, and the example is compact and directly usable. The sentence 'Keyword research for SEO' is redundant filler that could be cut.

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 4-parameter, fully documented, read-only lookup with no output schema, the description covers purpose, return fields, and a concrete invocation, which is nearly everything an agent needs. It would be complete with a note on API-key requirement consequences and per-call cost.

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%, including the _apiKey format, default language 'en', and location_code 2840 = United States, so the schema carries parameter meaning. The description only echoes the keywords/location_code example and adds no extra semantics, making baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and metrics: monthly search volume, keyword difficulty (0-100), CPC, and competition, plus the 10-keyword batch limit. It is immediately clear what the tool returns, though 'Keyword research for SEO' is a restatement rather than added distinction and no sibling scope boundary is drawn.

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

Usage Guidelines3/5

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

Usage is only implied by the phrase 'Keyword research for SEO' and the illustrative call. There is no statement of when to prefer this over other research tools or any exclusion, so an agent must infer the context.

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.