mcp-livedatapro

getSeoKeywordVolume

Get monthly search volume, Google Ads CPC, competition difficulty, and search intent for any keyword. Use when researching Google monthly search volume, YoY demand trends, Google Ads CPC (USD), and SEO keyword difficulty (0-100) for marketing or content planning. Do not use for finding expired domains (use searchExpiredDomains). Aggregates clickstream and Google Ads planner data by target ISO country.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "getSeoKeywordVolume"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	Yes	Target search phrase or keyword to analyze (2 to 100 characters).
`country_code`	No	2-letter uppercase ISO target market code (defaults to 'US').	US

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / country_code / default
```
Added value: +"US"
```
- addedInput schema / properties / country_code / examples
```
Added value: +[
+  "US"
+]
```
- addedInput schema / properties / country_code / pattern
```
Added value: +"^[A-Z]{2}$"
```
- addedInput schema / properties / keyword / examples
```
Added value: +[
+  "autonomous ai agents"
+]
```
- addedInput schema / properties / keyword / maxLength
```
Added value: +100
```
- addedInput schema / properties / keyword / minLength
```
Added value: +2
```

Changed2 schema fields changedOct 24, 2026

changedInput schema / properties / country_code / description

Previous value: -"2-letter target market ISO code (default US)"New value: +"2-letter uppercase ISO target market code (defaults to 'US')."

changedInput schema / properties / keyword / description

Previous value: -"Target search phrase or keyword"New value: +"Target search phrase or keyword to analyze (2 to 100 characters)."

First observedOct 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and usefully discloses data provenance: it aggregates clickstream and Google Ads planner data by ISO country. It also clarifies metric units/ranges such as CPC in USD and difficulty on a 0-100 scale, though it does not cover auth, rate limits, or exact response shape.

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 front-loaded with the core capability and then supplies use and exclusion guidance in a compact three-sentence block. Every sentence adds distinct value with no repetition.

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 low-complexity, two-parameter retrieval tool, the description covers the main metrics, data sources, country aggregation, and usage boundaries. The lack of an output schema means exact return structure is not fully specified, but the listed metrics provide enough context to call it correctly.

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 both parameters are already well documented in the schema. The description reinforces the country targeting concept with 'target ISO country' but adds little syntax or constraint detail beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource: getting monthly search volume, CPC, competition difficulty, and search intent for a keyword. It is immediately distinguishable from unrelated sibling tools and explicitly names searchExpiredDomains as a different use case.

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?

It gives explicit use cases such as researching Google monthly search volume, YoY demand trends, CPC, and SEO difficulty for marketing/content planning. It also includes an explicit exclusion: do not use for expired domains, and names searchExpiredDomains instead.

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

All mcp-livedatapro tools Inspect

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

Need Help?