PicassoWeb

Capture motion over time

capture_motion

Capture live motion from any webpage by sampling frames and numeric animation curves after load, scroll, hover, or click.

Instructions

Use this when you need to observe actual motion, especially JS-driven animation. Avoid it when declared CSS and WAAPI definitions are sufficient; use extract_animations. Sample frames, live animations, and numeric style curves after load, scroll, hover, or click. Cost: heavy. Session: uses one browser page for one URL. May write files when an output path is provided. Possible follow-ups if evidence is still missing: inspect_component, compare_replica.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Absolute http:// or https:// URL to capture motion from.
`samples`	No	Number of frames to capture.
`trigger`	No	What starts the motion: page load (reloads and samples immediately), scrolling, or hover/click on a selector.	load
`selector`	No	Required for hover/click; optional scroll target for the scroll trigger.
`outputDir`	No	Absolute directory to save all frames into as motion-frame-N.jpg.
`timeoutMs`	No	Navigation timeout in milliseconds.
`userAgent`	No	Optional browser user-agent override.
`waitUntil`	No	Page lifecycle event to await before extraction.	domcontentloaded
`intervalMs`	No	Target milliseconds between frames.
`maxAnimations`	No	Cap on Web Animations API entries returned.
`viewportWidth`	No	Browser viewport width in CSS pixels.
`trackSelectors`	No	Extra elements whose computed transform/opacity/filter/clip-path are sampled at every frame.
`viewportHeight`	No	Browser viewport height in CSS pixels.
`maxInlineFrames`	No	How many frames to return inline as images.
`maxTrackedElements`	No	Cap on elements sampled for numeric motion curves.
`allowPrivateNetwork`	No	Allow localhost and private-network URLs. Enable only for trusted sites.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Observed motion data; frame images are returned as MCP image content.
`guidance`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed7 schema fields changedv0.10.1Aug 28, 2026

addedOutput schema / properties / guidance

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "cost": {
+      "enum": [
+        "light",
+        "standard",
+        "heavy"
+      ],
+      "type": "string"
+    },
+    "nextTools": {
+      "description": "Candidate follow-ups; do not call them automatically or in parallel.",
+      "items": {
+        "enum": [
+          "analyze_site",
+          "analyze_html",
+          "inspect_component",
+          "capture_screenshot",
+          "extract_assets",
+          "extract_animations",
+          "extract_layout",
+          "clone_section",
+          "capture_interactions",
+          "extract_responsive",
+          "compare_replica",
+          "create_replication_kit",
+          "capture_motion",
+          "crawl_site"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "sessionPolicy": {
+      "enum": [
+        "offline-document",
+        "single-url",
+        "multi-viewport",
+        "dual-page",
+        "site-crawl"
+      ],
+      "type": "string"
+    },
+    "summary": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "tool": {
+      "const": "capture_motion",
+      "type": "string"
+    },
+    "warnings": {
+      "description": "Non-fatal limitations or incomplete evidence from this run.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "writesFiles": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "tool",
+    "summary",
+    "nextTools",
+    "warnings",
+    "cost",
+    "writesFiles",
+    "sessionPolicy"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / result / additionalProperties
```
Added value: +{}
```

addedOutput schema / properties / result / description

Added value: +"Observed motion data; frame images are returned as MCP image content."

addedOutput schema / properties / result / properties

Added value: +{
+  "animations": {
+    "items": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "frames": {
+    "items": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "metadata": {
+    "additionalProperties": {},
+    "properties": {
+      "analyzedAt": {
+        "type": "string"
+      },
+      "finalUrl": {
+        "type": "string"
+      },
+      "requestedUrl": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "requestedUrl",
+      "finalUrl",
+      "title",
+      "analyzedAt"
+    ],
+    "type": "object"
+  },
+  "trackedElements": {
+    "items": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "trigger": {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  "warnings": {
+    "description": "Non-fatal limitations or incomplete evidence from this run.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}

addedOutput schema / properties / result / required

Added value: +[
+  "metadata",
+  "trigger",
+  "animations",
+  "frames",
+  "trackedElements",
+  "warnings"
+]

addedOutput schema / properties / result / type
```
Added value: +"object"
```

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "result",
+  "guidance"
+]

Addedv0.10.0Aug 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: 'Cost: heavy', 'uses one browser page for one URL', and 'May write files when an output path is provided'. These details disclose side effects and resource impact not captured by the annotation flags, without contradicting them.

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 compact and front-loaded with the primary use case, followed by the exclusion, behavior, cost, session model, and follow-ups. Every sentence adds useful decision-making or safety information with no filler.

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

Completeness5/5

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

For a complex 16-parameter tool with an output schema and open-world implications, the description covers the essential operational context: heavy cost, single-page session, file-writing side effect, trigger types, and follow-ups. Nothing critical is missing for an agent to decide and use the tool effectively.

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 input schema already documents every parameter thoroughly. The description contributes high-level context like triggers and output files, but does not need to compensate for schema gaps. Baseline 3 applies.

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 states a specific purpose: observe actual motion, especially JS-driven animation, and sample frames, live animations, and numeric style curves. It explicitly distinguishes itself from extract_animations, so an agent can select between siblings without opening schemas.

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?

It gives explicit when-to-use ('Use this when you need to observe actual motion'), when-to-avoid ('Avoid it when declared CSS and WAAPI definitions are sufficient; use extract_animations'), and names likely follow-ups. This is direct routing guidance with no ambiguity.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/blackridder22/PicassoWeb'

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