Skip to main content
Glama

seo_keyword_difficulty

Analyze keyword difficulty for SEO strategies using the ReviewWebsite API. Input a keyword and optional country code to evaluate competition and optimize search rankings.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoYour ReviewWebsite API key
countryNoCountry code (default: us)
keywordYesThe keyword to check difficulty for

Implementation Reference

  • MCP tool handler function that executes the logic for 'seo_keyword_difficulty' by calling the reviewWebsiteController.getKeywordDifficulty method.
    async function handleGetKeywordDifficulty(
    	args: SeoKeywordDifficultyToolArgsType,
    ) {
    	const methodLogger = Logger.forContext(
    		'tools/reviewwebsite.tool.ts',
    		'handleGetKeywordDifficulty',
    	);
    	methodLogger.debug(`Getting keyword difficulty:`, {
    		...args,
    		api_key: args.api_key ? '[REDACTED]' : undefined,
    	});
    
    	try {
    		const result = await reviewWebsiteController.getKeywordDifficulty(
    			args.keyword,
    			{
    				country: args.country,
    			},
    			{
    				api_key: args.api_key,
    			},
    		);
    
    		return {
    			content: [
    				{
    					type: 'text' as const,
    					text: result.content,
    				},
    			],
    		};
    	} catch (error) {
    		methodLogger.error(`Error getting keyword difficulty`, error);
    		return formatErrorForMcpTool(error);
    	}
    }
  • Registration of the 'seo_keyword_difficulty' tool with the MCP server, linking name, description, input schema, and handler function.
    server.tool(
    	'seo_keyword_difficulty',
    	`Get keyword difficulty for a keyword using ReviewWeb.site API.`,
    	SeoKeywordDifficultyToolArgs.shape,
    	handleGetKeywordDifficulty,
    );
  • Zod schema defining the input arguments for the 'seo_keyword_difficulty' tool.
    export const SeoKeywordDifficultyToolArgs = z.object({
    	keyword: z.string().describe('The keyword to check difficulty for'),
    	country: z.string().optional().describe('Country code (default: us)'),
    	api_key: z.string().optional().describe('Your ReviewWebsite API key'),
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic function without disclosing behavioral traits such as rate limits, authentication needs (implied by api_key but not explained), error handling, or response format. It mentions the API source but adds minimal operational context.

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 with zero waste, front-loading the core purpose. It's appropriately sized for the tool's complexity, avoiding unnecessary elaboration.

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 no annotations, no output schema, and a mutation-like tool (fetching external data), the description is incomplete. It lacks details on return values, error cases, or operational constraints, leaving significant gaps for an AI agent to use it effectively.

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 parameters like 'api_key', 'country', and 'keyword'. The description adds no extra meaning beyond implying the API context, meeting the baseline for high schema coverage without compensating with additional insights.

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 difficulty') and target resource ('for a keyword'), specifying it uses the ReviewWeb.site API. However, it doesn't differentiate from sibling tools like 'seo_keyword_ideas' or 'seo_traffic' beyond the core function, missing explicit distinction.

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?

No guidance is provided on when to use this tool versus alternatives like 'seo_keyword_ideas' or 'seo_traffic'. The description lacks context about typical use cases, prerequisites, or exclusions, offering only a basic functional statement.

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