Best Keyword Research API: This Keyword Tool API Find millions of keyword suggestions for your SEO..
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 2.9/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. Every (and the only) tool has a clearly distinct purpose by virtue of being unique.
The single tool name 'get_keyword_research' follows a consistent verb_noun pattern. Since there is only one tool, naming consistency is trivially maintained.
The server has only one tool, which feels thin for a general-purpose API. While it is not trivial, the scope is minimal and agents may need more operations to fully utilize the domain.
The server only offers a single 'get' operation, covering the core querying functionality but lacking any supporting operations like pagination, source selection, or result filtering. This makes the surface notably incomplete for a comprehensive keyword research workflow.
get_keyword_researchKeyword ResearchCInspectFind millions of keyword suggestions for your SEO. Enter a topic and get your list of best keywords for you Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | ||
| keyword | No | ||
| languagecode | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavior. It mentions billing ('Billing per call: 1 Credits') and implies a list output, but it does not clarify response structure, rate limits, authentication needs, data source, or limitations. This is insufficient disclosure for a tool with zero annotation support.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded with the core purpose. However, the sentence 'list of best keywords for you Billing per call: 1 Credits' has a grammar/punctuation flaw and awkwardly merges billing into the main sentence, reducing structural polish.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, no annotations, and no coverage for three parameters. The description explains the general use case and one input concept, but it omits critical details about country/language behavior, return format, and edge cases, making it incomplete for effective tool invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It loosely equates the 'keyword' parameter with a 'topic,' but it does not explain the 'country' or 'languagecode' parameters at all. Only partial meaning is added beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with 'Find millions of keyword suggestions for your SEO' and 'get your list of best keywords.' This is a specific verb+resource pairing, though the grammar is awkward and it does not distinguish from sibling tools (none provided).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives implied usage context ('for your SEO' and 'Enter a topic'), but it does not explicitly state when to use this tool versus alternatives or provide any exclusions or prerequisites. This is usable but not strongly instructive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
