Skip to main content
Glama

seo_keyword_ideas

Generate targeted keyword ideas for SEO optimization using ReviewWeb.site API. Specify a keyword, country, and search engine to refine results and enhance content strategy.

Instructions

Get keyword ideas for a keyword using ReviewWeb.site API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoYour ReviewWebsite API key
countryNoCountry code (default: us)
keywordYesThe keyword to get ideas for
searchEngineNoSearch engine to use (default: Google)

Implementation Reference

  • MCP handler function that executes the seo_keyword_ideas tool logic by calling the controller and formatting the MCP response.
    async function handleGetKeywordIdeas(args: SeoKeywordIdeasToolArgsType) {
    	const methodLogger = Logger.forContext(
    		'tools/reviewwebsite.tool.ts',
    		'handleGetKeywordIdeas',
    	);
    	methodLogger.debug(`Getting keyword ideas:`, {
    		...args,
    		api_key: args.api_key ? '[REDACTED]' : undefined,
    	});
    
    	try {
    		const result = await reviewWebsiteController.getKeywordIdeas(
    			args.keyword,
    			{
    				country: args.country,
    				searchEngine: args.searchEngine,
    			},
    			{
    				api_key: args.api_key,
    			},
    		);
    
    		return {
    			content: [
    				{
    					type: 'text' as const,
    					text: result.content,
    				},
    			],
    		};
    	} catch (error) {
    		methodLogger.error(`Error getting keyword ideas`, error);
    		return formatErrorForMcpTool(error);
    	}
    }
  • Registration of the seo_keyword_ideas tool with the MCP server, specifying name, description, input schema, and handler.
    server.tool(
    	'seo_keyword_ideas',
    	`Get keyword ideas for a keyword using ReviewWeb.site API.`,
    	SeoKeywordIdeasToolArgs.shape,
    	handleGetKeywordIdeas,
    );
  • Zod schema defining input arguments for the seo_keyword_ideas tool.
    export const SeoKeywordIdeasToolArgs = z.object({
    	keyword: z.string().describe('The keyword to get ideas for'),
    	country: z.string().optional().describe('Country code (default: us)'),
    	searchEngine: z
    		.string()
    		.optional()
    		.describe('Search engine to use (default: Google)'),
    	api_key: z.string().optional().describe('Your ReviewWebsite API key'),
    });
  • Service function that performs the actual HTTP POST request to the ReviewWeb.site API endpoint for generating SEO keyword ideas.
    async function getKeywordIdeas(
    	keyword: string,
    	options?: SeoKeywordIdeasOptions,
    	apiKey?: string,
    ): Promise<any> {
    	const methodLogger = Logger.forContext(
    		'services/vendor.reviewwebsite.service.ts',
    		'getKeywordIdeas',
    	);
    
    	try {
    		methodLogger.debug('Getting keyword ideas', { keyword, options });
    
    		const response = await axios.post(
    			`${API_BASE}/seo-insights/keyword-ideas`,
    			{
    				keyword,
    				country: options?.country,
    				searchEngine: options?.searchEngine,
    			},
    			{
    				headers: getHeaders(apiKey),
    			},
    		);
    
    		methodLogger.debug('Successfully got keyword ideas');
    		return response.data;
    	} catch (error) {
    		return handleApiError(error, 'getKeywordIdeas');
    	}
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'gets keyword ideas' but doesn't explain what that entails—such as whether it performs external API calls, requires authentication via api_key, returns structured data, or has rate limits. This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool involves external API interaction (implied by 'using ReviewWeb.site API') and has no annotations or output schema, the description is insufficient. It doesn't cover authentication needs (api_key parameter), response format, error handling, or how it differs from sibling SEO tools, leaving the agent under-informed for effective use.

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 fully documents all four parameters (api_key, country, keyword, searchEngine). The description adds no additional semantic context beyond implying the keyword is the input for generating ideas, which aligns with the schema. This meets the baseline for high schema coverage.

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 clearly states the action ('Get keyword ideas') and the resource ('for a keyword'), specifying it uses the ReviewWeb.site API. However, it doesn't distinguish this tool from sibling SEO tools like 'seo_keyword_difficulty' or 'seo_traffic', which reduces clarity about its specific role in the SEO toolkit.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'seo_keyword_difficulty' or 'seo_traffic'. It mentions the API but doesn't specify prerequisites, ideal use cases, or exclusions, leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrgoonie/reviewwebsite-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server