Skip to main content
Glama

summarize_website

Extract and condense website content into concise summaries using AI. Customize output format, length, and processing parameters for efficient web information review.

Instructions

Summarize a website (and its internal links) using AI via ReviewWeb.site API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoYour ReviewWebsite API key
debugNoEnable debug mode for detailed logging
delayAfterLoadNoOptional delay after page load in milliseconds
formatNoFormat of the summary (bullet points or paragraph)
instructionsNoCustom instructions for the AI on how to summarize the content
maxLengthNoMaximum length of the summary in words
maxLinksNoMaximum number of pages to process
modelNoAI model to use for summarization
systemPromptNoCustom system prompt to guide the AI
urlYesThe main URL of the website to summarize

Implementation Reference

  • The MCP tool handler function that implements the core logic for the 'summarize_website' tool. It processes arguments, calls the ReviewWebsite controller's summarizeWebsite method, formats the response for MCP, and handles errors.
    async function handleSummarizeWebsite(args: SummarizeWebsiteToolArgsType) {
    	const methodLogger = Logger.forContext(
    		'tools/reviewwebsite.tool.ts',
    		'handleSummarizeWebsite',
    	);
    	methodLogger.debug(`Summarizing website with options:`, {
    		...args,
    		api_key: args.api_key ? '[REDACTED]' : undefined,
    	});
    
    	try {
    		const result = await reviewWebsiteController.summarizeWebsite(
    			args.url,
    			{
    				instructions: args.instructions,
    				systemPrompt: args.systemPrompt,
    				model: args.model,
    				delayAfterLoad: args.delayAfterLoad,
    				maxLinks: args.maxLinks,
    				maxLength: args.maxLength,
    				format: args.format,
    				debug: args.debug,
    			},
    			{
    				api_key: args.api_key,
    			},
    		);
    
    		return {
    			content: [
    				{
    					type: 'text' as const,
    					text: result.content,
    				},
    			],
    		};
    	} catch (error) {
    		methodLogger.error(`Error summarizing website`, error);
    		return formatErrorForMcpTool(error);
    	}
    }
  • The registration of the 'summarize_website' tool with the MCP server, specifying name, description, input schema, and handler function.
    server.tool(
    	'summarize_website',
    	`Summarize a website (and its internal links) using AI via ReviewWeb.site API.`,
    	SummarizeWebsiteToolArgs.shape,
    	handleSummarizeWebsite,
    );
  • Zod schema defining the input arguments for the 'summarize_website' tool, including URL, instructions, model options, limits, and API key.
    export const SummarizeWebsiteToolArgs = z.object({
    	url: z.string().describe('The main URL of the website to summarize'),
    	instructions: z
    		.string()
    		.optional()
    		.describe(
    			'Custom instructions for the AI on how to summarize the content',
    		),
    	systemPrompt: z
    		.string()
    		.optional()
    		.describe('Custom system prompt to guide the AI'),
    	model: z.string().optional().describe('AI model to use for summarization'),
    	delayAfterLoad: z
    		.number()
    		.optional()
    		.describe('Optional delay after page load in milliseconds'),
    	maxLinks: z
    		.number()
    		.optional()
    		.describe('Maximum number of pages to process'),
    	maxLength: z
    		.number()
    		.optional()
    		.describe('Maximum length of the summary in words'),
    	format: z
    		.enum(['bullet', 'paragraph'])
    		.optional()
    		.describe('Format of the summary (bullet points or paragraph)'),
    	debug: z
    		.boolean()
    		.optional()
    		.describe('Enable debug mode for detailed logging'),
    	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, the description carries full burden but provides minimal behavioral insight. It mentions AI summarization and internal links but doesn't cover rate limits, authentication needs (implied by api_key parameter), error handling, or what 'summarize' entails operationally.

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?

Single sentence is appropriately concise and front-loaded with core purpose. However, it could be more structured by separating API context from functionality.

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?

For a complex tool with 10 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the summary output looks like, how internal links are processed, or provide essential context for AI-driven behavior.

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 parameters are well-documented in the schema. The description adds marginal value by hinting at 'internal links' processing, which relates to 'maxLinks' parameter, but doesn't significantly enhance understanding beyond the schema.

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 ('summarize') and resource ('website'), and specifies it uses AI via a particular API. However, it doesn't explicitly differentiate from sibling tools like 'summarize_url' or 'summarize_multiple_urls' beyond mentioning internal links.

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 on when to use this tool versus alternatives like 'summarize_url' or 'summarize_multiple_urls'. The mention of 'internal links' hints at broader scope but doesn't provide explicit usage context or exclusions.

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