Skip to main content
Glama
ALIEX7664

Puppeteer Debugger MCP Server

by ALIEX7664

take_screenshot

Take screenshots of web pages using Puppeteer. Capture viewport or full-page. Choose output mode: base64 inline, file, or auto based on size. Designed for debugging and visual inspection.

Instructions

截图工具(辅助调试)。支持视口截图和全页截图。建议在使用前询问用户希望的输出方式:如果用户需要直接查看图片,使用 inline 模式返回 base64;如果用户需要保存图片文件,使用 file 或 auto 模式保存为文件。对于全页截图或大图片,强烈建议使用 file/auto 模式避免响应过大。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo页面 URL(可选)
fullPageNo是否截取整页。true 表示截取整个页面(包括需要滚动才能看到的内容),false 表示只截取当前视口可见部分。全页截图会自动触发懒加载内容,确保完整截图。
outputModeNo输出模式(建议在使用前询问用户偏好): - auto:根据图片大小自动选择(小于阈值返回 base64,大于阈值保存为文件,默认阈值 100KB) - file:始终保存为文件,返回文件路径(适合用户明确需要保存文件的情况) - inline:始终返回 base64 编码的图片数据(适合用户需要直接查看小图片的情况,不推荐用于全页截图,因为会导致响应过大) 选择建议: - 如果用户说"截图"、"保存截图"、"下载截图"等,使用 file 或 auto 模式 - 如果用户说"显示截图"、"查看截图"、"预览截图"等,且图片较小(非全页),可以使用 inline 模式 - 如果用户未明确说明,或进行全页截图,默认使用 auto 模式 - 如果不确定用户需求,建议询问:"您希望截图以什么方式返回?1) 保存为文件(推荐,适合大图片) 2) 直接返回图片数据(仅适合小图片)"auto
filePathNo文件保存路径(可选,仅在 file/auto 模式时有效)。如果未指定,默认保存到 ./screenshots/screenshot-{timestamp}-{random}.png。可以使用相对路径(相对于 MCP Server 工作目录)或绝对路径。
maxBase64SizeKBNoauto 模式阈值(KB,base64 大小,默认 100KB)。当 auto 模式下,如果图片的 base64 大小超过此阈值,会自动保存为文件;否则返回 base64。
scrollDelayNo滚动后等待时间(毫秒,用于触发懒加载,默认 1000)
waitForSelectorNo等待特定选择器加载(可选,字符串)
Behavior4/5

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

With no annotations, the description must fully cover behavioral traits. It explains that inline returns base64, file/auto saves to file, and that full-page screenshots may trigger lazy loading. However, it does not mention prerequisites like needing a page to be loaded first.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose, especially the outputMode section which largely repeats information found in the schema. While organized with bullet points, it could be more concise to improve readability.

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

Completeness4/5

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

Given 7 parameters with full schema descriptions, no required parameters, and no output schema, the description offers robust usage guidance and covers decision-making for output modes. However, it could mention what happens when no URL is provided.

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 baseline is 3. The description adds some context (e.g., asking user for output mode) but much of the parameter guidance is already in the schema descriptions. The added value is limited.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it's a screenshot tool for debugging, supporting viewport and full-page screenshots. It distinguishes itself from sibling tools which have different purposes (memory analysis, element checking, etc.).

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use each output mode (inline vs file/auto) and recommends asking the user for preference. It also advises against using inline for full-page or large images, and suggests defaulting to auto when uncertain.

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

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/ALIEX7664/puppeteer-debugger-mcp-server'

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