Skip to main content
Glama

summarize_url

Summarize web page content from any URL into concise bullet points or paragraphs using AI. Customize output length, format, and instructions for tailored summaries.

Instructions

Summarize a web page URL 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
modelNoAI model to use for summarization
systemPromptNoCustom system prompt to guide the AI
urlYesThe URL to summarize

Implementation Reference

  • MCP tool handler that processes arguments for summarize_url, calls reviewWebsiteController.summarizeUrl, and returns formatted MCP response.
    async function handleSummarizeUrl(args: SummarizeUrlToolArgsType) {
    	const methodLogger = Logger.forContext(
    		'tools/reviewwebsite.tool.ts',
    		'handleSummarizeUrl',
    	);
    	methodLogger.debug(`Summarizing URL with options:`, {
    		...args,
    		api_key: args.api_key ? '[REDACTED]' : undefined,
    	});
    
    	try {
    		const result = await reviewWebsiteController.summarizeUrl(
    			args.url,
    			{
    				instructions: args.instructions,
    				systemPrompt: args.systemPrompt,
    				model: args.model,
    				delayAfterLoad: args.delayAfterLoad,
    				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 URL`, error);
    		return formatErrorForMcpTool(error);
    	}
    }
  • Registration of the summarize_url tool with the MCP server, specifying name, description, input schema, and handler function.
    	'summarize_url',
    	`Summarize a web page URL using AI via ReviewWeb.site API.`,
    	SummarizeUrlToolArgs.shape,
    	handleSummarizeUrl,
    );
  • Zod schema defining the input parameters for the summarize_url tool.
    export const SummarizeUrlToolArgs = z.object({
    	url: z.string().describe('The URL 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'),
    	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'),
    });
  • Service helper function that performs the actual API request to ReviewWeb.site's /summarize/url endpoint.
    async function summarizeUrl(
    	url: string,
    	options?: SummarizeOptions,
    	apiKey?: string,
    ): Promise<any> {
    	const methodLogger = Logger.forContext(
    		'services/vendor.reviewwebsite.service.ts',
    		'summarizeUrl',
    	);
    
    	try {
    		methodLogger.debug('Summarizing URL', { url, options });
    
    		const response = await axios.post(
    			`${API_BASE}/summarize/url`,
    			{
    				url,
    				options,
    			},
    			{
    				headers: getHeaders(apiKey),
    			},
    		);
    
    		methodLogger.debug('Successfully summarized URL');
    		return response.data;
    	} catch (error) {
    		return handleApiError(error, 'summarizeUrl');
    	}
    }
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 the API method but doesn't describe key behaviors: whether it requires authentication (implied by 'api_key' parameter but not stated), rate limits, error handling, output format (beyond format parameter), or what happens with invalid URLs. For a tool with 9 parameters and no annotation coverage, this is a significant gap in transparency.

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 states the core purpose without redundancy. It's front-loaded with the key action and resource, and every word earns its place by specifying the method ('using AI via ReviewWeb.site API'). No unnecessary details or fluff are included.

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 complexity (9 parameters, no annotations, no output schema), the description is incomplete. It doesn't address authentication needs, error cases, output structure, or how to interpret results. For an AI summarization tool with multiple configurable parameters, more context is needed to guide effective use, especially without annotations or output schema to fill gaps.

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 9 parameters. The description adds no additional parameter semantics beyond what's in the schema—it doesn't explain parameter interactions, defaults, or practical examples. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 ('web page URL') with the method ('using AI via ReviewWeb.site API'). It distinguishes from siblings like 'scrape_url' or 'extract_data' by focusing on summarization rather than extraction or scraping. However, it doesn't explicitly differentiate from 'summarize_multiple_urls' or 'summarize_website' beyond the singular vs. plural 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 'summarize_multiple_urls' for multiple URLs or 'summarize_website' for broader website analysis. The description lacks context about prerequisites (e.g., needing an API key) or typical use cases, 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