Skip to main content
Glama
Djsand
by Djsand

Analyze Motion

analyze_motion

Analyze webpage motion by sampling keyframes, extracting CSS animation metadata, and generating pixel diffs with a contact sheet for coding agents.

Instructions

Analyze rendered page motion for coding agents using sampled keyframes, CSS animation metadata, pixel diffs, and a contact sheet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe public http(s) URL to render and analyze.
widthNoViewport width in pixels.
heightNoViewport height in pixels.
outputDirNoDirectory where motion analysis evidence should be saved.
timeoutMsNoNavigation and analysis timeout.
waitUntilNoNavigation wait condition. Defaults to load for motion analysis.
durationMsNoHow long to sample motion after navigation. Defaults to 3000 ms.
sampleCountNoNumber of screenshots to sample across the duration. Defaults to 5.
scrollStepPxNoPixels to scroll per step when sampling scroll motion.
includeImagesNoEmbed contact sheet and diff image resources in the MCP response. Defaults to true.
scrollDelayMsNoDelay between scroll steps in milliseconds.
scrollMaxStepsNoMaximum number of scroll steps.
changeThresholdNoPer-pixel channel delta threshold for pixel-diff detection. Defaults to 40.
diffSampleStrideNoPixel sampling stride for diff analysis. Higher values are faster but less precise. Defaults to 2.
includePixelDiffNoCompute pixel-diff summaries across sampled frames. Defaults to true.
includeFrameImagesNoAlso embed each raw sampled frame as an image resource. Defaults to false.
allowPrivateNetworkNoAllow localhost/private network URLs for this call. Defaults to false.
scrollDuringCaptureNoScroll through the page while sampling to analyze scroll-driven motion and lazy loading.
includeCssAnimationsNoExtract document.getAnimations() metadata from the page. Defaults to true.
Behavior2/5

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

With no annotations, the description must disclose side effects and safety. It mentions the analysis techniques but not that the tool renders a page, may write files via outputDir, or whether it's read-only. Missing information about navigation or resource consumption.

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?

The description is a single sentence that is reasonably concise and front-loads the main purpose. It includes a few extra words like 'for coding agents' but is not bloated.

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?

Despite 19 parameters and no output schema, the description is too brief. It doesn't explain the output format, return value, or workflow, leaving the agent with insufficient context for a complex tool. The parameter schema helps but doesn't fill the output gap.

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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds no extra meaning about parameters, and only indirectly hints at sampling and diffs without referencing specific parameters.

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 tool analyzes page motion, specifying the methods (keyframes, CSS animations, pixel diffs, contact sheet). This is a specific verb+resource combination, but it doesn't explicitly distinguish from the sibling capture_motion, so not a 5.

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 vs alternatives. It doesn't mention use cases, exclusions, or refer to sibling tools like capture_motion or capture_page. The only context is implied by the parameter names.

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/Djsand/renderproof'

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