Skip to main content
Glama
api-freaks

@apifreaks/mcp

by api-freaks
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Screenshot Capture Scrolling

screenshot_capture_scrolling
Read-onlyIdempotent

Record a scrolling video or animated GIF of any webpage and get a downloadable link in JSON format. Supports MP4, WebM, or GIF output.

Instructions

Record a scrolling video or animated GIF of a webpage and return a JSON response containing the video download URL. Always ask the user before calling this tool:

  • What format? MP4 (default, best compatibility), WebM (smaller), or GIF (looping animation)?

  • How long should it scroll — how many seconds (up to 60)?

  • Scroll speed: slow, normal, or fast?

  • Should it scroll back to the top after reaching the bottom (great for looping GIFs)?

  • Any specific viewport size to simulate?

Use screenshot_capture instead for static screenshots (PNG, JPG, PDF).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull URL of the webpage to screenshot (e.g. 'https://example.com').
file_typeNoOutput video format: MP4 (default, broadest compatibility), WEBM (smaller size), or GIF (looping animation).MP4
scroll_speedNoScroll speed: 'fast', 'normal' (default), or 'slow'.normal
durationNoHow many seconds the scrolling should last (0–60). If left unset, it will take however long it takes to scroll the website.
scroll_backNoIf true, the page scrolls to the bottom then back to the top. Ideal for looping GIFs.
widthNoViewport width in pixels (default 1680, max 7680). Use to simulate specific device widths (e.g. 375 for iPhone, 768 for tablet).
heightNoViewport height in pixels (default 867, max 4320).
no_cookie_bannersNoBlock cookie consent banners before rendering for a clean, overlay-free screenshot.
block_adsNoBlock advertisements before rendering.
dark_modeNoEnable dark mode for websites that support it via CSS prefers-color-scheme.
delayNoDelay in milliseconds before rendering begins. Useful to let animations finish or dynamic content settle after page load.

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, which already convey safety and idempotency. The description adds context about the output being a video download URL and the need for user input, but does not contradict annotations.

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 concise, front-loaded with the core function, and well-structured with a list of user questions. Every sentence adds value, no fluff.

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 the tool's 11 parameters and no output schema, the description explains the return format (JSON with download URL) sufficiently. It does not detail error conditions but is reasonably complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed parameter descriptions. The description adds value by explaining the purpose of parameters like scroll_back for looping GIFs and providing questions to ask the user, enhancing understanding beyond the schema.

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 records a scrolling video or animated GIF of a webpage and returns a JSON with download URL. It distinguishes itself from the sibling 'screenshot_capture' for static screenshots.

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?

Provides explicit instructions to always ask the user about key parameters (format, duration, scroll speed, etc.) and when to use the alternative static screenshot tool. Excellent guidance for an AI agent.

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/api-freaks/apifreaks-mcp'

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