Skip to main content
Glama

seo_traffic

Analyze website traffic for any domain or URL using ReviewWeb.site API. Specify mode (subdomains or exact) and country code for precise insights on visitor data.

Instructions

Check traffic for a domain or URL using ReviewWeb.site API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoYour ReviewWebsite API key
countryNoCountry code (default: None)
domainOrUrlYesThe domain or URL to check traffic for
modeNoMode to use (default: subdomains)

Implementation Reference

  • MCP tool handler function that executes the 'seo_traffic' tool logic by calling the ReviewWebsite controller's getTraffic method and formatting the response.
    async function handleGetTraffic(args: SeoTrafficToolArgsType) {
    	const methodLogger = Logger.forContext(
    		'tools/reviewwebsite.tool.ts',
    		'handleGetTraffic',
    	);
    	methodLogger.debug(`Checking traffic:`, {
    		...args,
    		api_key: args.api_key ? '[REDACTED]' : undefined,
    	});
    
    	try {
    		const result = await reviewWebsiteController.getTraffic(
    			args.domainOrUrl,
    			{
    				mode: args.mode,
    				country: args.country,
    			},
    			{
    				api_key: args.api_key,
    			},
    		);
    
    		return {
    			content: [
    				{
    					type: 'text' as const,
    					text: result.content,
    				},
    			],
    		};
    	} catch (error) {
    		methodLogger.error(`Error checking traffic`, error);
    		return formatErrorForMcpTool(error);
    	}
    }
  • Registration of the 'seo_traffic' tool with the MCP server, specifying name, description, input schema, and handler function.
    server.tool(
    	'seo_traffic',
    	`Check traffic for a domain or URL using ReviewWeb.site API.`,
    	SeoTrafficToolArgs.shape,
    	handleGetTraffic,
    );
  • Zod schema definition for the input arguments of the 'seo_traffic' tool.
    export const SeoTrafficToolArgs = z.object({
    	domainOrUrl: z.string().describe('The domain or URL to check traffic for'),
    	mode: z
    		.enum(['subdomains', 'exact'])
    		.optional()
    		.describe('Mode to use (default: subdomains)'),
    	country: z.string().optional().describe('Country code (default: None)'),
    	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 the full burden of behavioral disclosure. It mentions using an external API ('ReviewWeb.site API'), which implies potential rate limits, authentication needs (via api_key parameter), and network dependencies. However, it doesn't specify what 'traffic' entails (e.g., metrics like visits, sources), whether it's read-only (likely, but not stated), or any error handling. The description adds minimal context beyond the basic action.

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 front-loads the core purpose ('Check traffic for a domain or URL') and specifies the method ('using ReviewWeb.site API'). There's no wasted verbiage, repetition, or unnecessary details, making it highly concise and well-structured for quick understanding.

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

Completeness3/5

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

Given the tool's moderate complexity (4 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic action and API source but lacks details on output format, error cases, or integration context. Without annotations or an output schema, the agent must infer behavior from the description alone, which is incomplete for reliable use (e.g., doesn't specify what 'traffic' data is returned).

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, domainOrUrl, mode) with descriptions and enum values. The description adds no additional parameter semantics beyond implying 'domainOrUrl' is the target and 'api_key' is for authentication. This meets the baseline of 3 where the schema does the heavy lifting, but the description doesn't compensate with extra insights like format examples or default behaviors.

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 ('check traffic') and target ('for a domain or URL') using the specific API ('ReviewWeb.site API'). It distinguishes from siblings like 'seo_backlinks' or 'seo_keyword_difficulty' by focusing on traffic metrics rather than backlinks or keywords. However, it doesn't explicitly contrast with all siblings (e.g., 'extract_data' could overlap in some contexts).

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. It doesn't mention when traffic checking is appropriate compared to other SEO tools like 'seo_backlinks' or general data extraction tools like 'extract_data'. There's no context about prerequisites (e.g., needing an API key) or typical use cases beyond the basic action.

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