Exepal

Keyword ideas

seo_keywords

Read-onlyIdempotent

Keyword research: up to 50 keyword ideas for a seed keyword with monthly searches, difficulty, cost per click and intent. Use to find what people search for around a topic before writing a page or picking keywords to track. One country per call. Returns seed, count and keywords[] {keyword, volume, difficulty 0-100, cpc, intent}. Not charged when the data source fails. Price: $0.05 per call from Exepal credit; not charged if the call fails.

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": {
      "seed": "<seed>"
    },
    "name": "seo_keywords"
  }
}

Input Schema

Name	Required	Description	Default
`seed`	Yes	A keyword or topic, e.g. crm for startups
`country`	No	Two-letter country, default us

Output Schema

Name	Required	Description	Default
`seed`	No
`count`	No
`country`	No
`keywords`	No
`language`	No
`generatedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), and the description adds value on top: a 50-result cap, one-country-per-call restriction, explicit billing ($0.05 per call) and the failure-billing exemption. Those commercial and limit details are not derivable from structured fields and matter before invoking.

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?

Front-loaded with purpose, then output shape, then constraints and pricing — good ordering. Slightly redundant: the no-charge-on-failure policy is stated twice ('Not charged when the data source fails' and 'not charged if the call fails'), costing a sentence.

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?

An output schema exists, yet the description still summarizes the return shape (seed, count, keywords[] with volume, difficulty 0-100, cpc, intent), which is helpful rather than required. Limits, cost, and country constraint are all covered for a simple two-parameter tool.

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 the baseline is 3, but the description adds real meaning: 'seed' is scoped as a topic/keyword that yields up to 50 ideas, and 'country' is constrained to a single country per call with a default of us. That adds operational semantics beyond the field descriptions.

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?

Specific verb and resource ('Keyword research: up to 50 keyword ideas for a seed keyword') plus the exact metrics returned. The line about 'before writing a page or picking keywords to track' implicitly separates it from tracking/gap siblings like seo_rank and seo_gap, so an agent can route without opening the schema.

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?

Gives a concrete usage context: use it to discover what people search for around a topic before writing a page or choosing keywords to track. It also states the operational constraint 'One country per call.' It stops short of naming alternatives or explicit when-not conditions.

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

All Exepal 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?