Skip to main content
Glama

record

Headlessly capture a web app in a Chromium browser, upload it to Clipy, and return a share link for sharing or AI review.

Instructions

Record a web app HEADLESSLY and upload it as a Clipy recording, then return its share link + agent-context URL. Use this to capture the outcome of work you just did — e.g. after building a feature, record the running app so it can be shared or read back. Opens the given URL in a headless Chromium (works in cloud sandboxes, no display needed), records for durationSeconds, and streams the video into Clipy's pipeline. Set type so the summary reads the recording correctly, viewports to sweep multiple screen sizes into one video, and storageState/initScript/userDataDir to record behind a login. Requires (1) Playwright installed in this MCP server's environment (npm i -g playwright && npx playwright install chromium) and (2) the CLIPY_API_KEY to carry the 'ingest' scope. Recording the REAL Mac screen or a specific window (ScreenCaptureKit, real logged-in browser) is CLI-only — clipy record --source mac-screen --window "<app>" — and not available via MCP. Quick per-cookie / per-localStorage-key injection (the CLI's --cookie / --local-storage) is a CLI-only convenience; storageState covers the same need here. The result reports the RESOLVED capture source (source: the post-redirect URL, page title and viewport actually being recorded) — compare it against the surface your driver is acting on BEFORE doing minutes of work, because Clipy will never focus or foreground a window or tab for you. Auth note: storageState seeds exactly what it contains (cookies + localStorage) but can't reproduce a whole browser identity (IndexedDB, service workers, some cross-origin auth); for those, produce a storageState via an interactive npx playwright open --save-storage=state.json <login-url> first, or use userDataDir pointed at a DEDICATED (never live) profile directory. After it returns, call wait_for_artifacts then get_agent_context to read the transcript/summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe http(s) URL to open and record (e.g. http://localhost:3000).
nameNoOptional title for the recording.
typeNoWhat the recording IS, so the AI summary doesn't misread it. One of: bug_report, feature_request, product_demo, walkthrough_tutorial, feedback_review, discussion_talk, other (aliases like bug/feature/demo/tutorial/review/talk accepted).
notesNoTimestamped narration notes describing what the recording shows. Headless captures are silent, so these notes BECOME the recording's transcript — write them like chapters ('0s: homepage loads', '8s: the new export button appears').
widthNoViewport + video width (default 1280). Ignored when `viewports` is set.
heightNoViewport + video height (default 720). Ignored when `viewports` is set.
viewportsNoRecord several screen sizes sequentially into ONE video (for cross-size demos). Comma-separated aliases (mobile,tablet,desktop) or WIDTHxHEIGHT (e.g. '390x844,1440x900'). The frame is sized to the largest; each pass slow-scrolls the page and gets an auto chapter note. When set, width/height are ignored.
initScriptNoPath to a JS file run in the page before every navigation (context.addInitScript) — e.g. to seed localStorage or stub an API. Contents are never logged.
descriptionNoOptional description for the recording.
userDataDirNoPath to a Chromium user-data ROOT — the dir holding 'Local State' plus profile subdirs (macOS Chrome: ~/Library/Application Support/Google/Chrome). WITHOUT profileDirectory, Clipy opens this dir's 'Default' profile directly and writes to it, so it is refused while a live Chrome holds it locked (quit Chrome first). WITH profileDirectory, Clipy COPIES that named profile into a temporary root and records the copy — your real profile is never opened or modified. A profile SUBDIR passed as the root is refused. Mutually exclusive with storageState.
storageStateNoPath to a Playwright storageState JSON (cookies + localStorage) to record behind a login. Passed unchanged to the browser context; its contents are never logged. Mutually exclusive with userDataDir.
durationSecondsNoHow long to record after the page loads, per viewport pass (default 15, max 300).
profileDirectoryNoWhich profile INSIDE userDataDir to record — 'Default', 'Profile 1', 'Profile 2', … (exact folder name from chrome://version → 'Profile Path'). Clipy COPIES that profile into a temporary scratch root (as its Default) and records the copy: your real profile is never opened or modified, and the copy is deleted after upload. The result discloses the copy. Requires userDataDir. (Playwright strips Chromium's --profile-directory, so copying is the only way to select a named profile.)
Behavior5/5

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

With no annotations, the description fully discloses behavior: headless Chromium in cloud sandbox, no display needed, records for durationSeconds, resolves capture source, never focuses windows. Details limitations: storageState cannot reproduce whole browser identity; userDataDir writing to live profile requires Chrome quit; copy behavior with profileDirectory. All critical behavioral traits are covered.

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 long but front-loaded with core purpose. It is structured with logical sections (usage, requirements, limitations, post-recording steps). While verbose, every sentence adds value given the tool's complexity. Slightly more structure (bullet points) could improve scanability, but it remains appropriately sized.

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?

The tool has 13 parameters, no output schema, and significant complexity. The description explains return values (share link, agent-context URL, resolved source), post-recording workflow (wait_for_artifacts, get_agent_context), prerequisites, and detailed auth scenarios. It is complete for an agent to understand and use 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%, so baseline 3. The description adds meaning beyond schema by explaining relationships: notes become transcript, viewports overrides width/height, initScript contents are never logged, userDataDir and storageState mutual exclusivity, etc. It clarifies context and constraints, raising the score to 4.

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 the tool records a web app headlessly and uploads as a Clipy recording, returning a share link and agent-context URL. It specifies the action ('record', 'upload', 'return'), the resource ('web app', 'Clipy recording'), and distinguishes from CLI-only methods (mac-screen, --cookie).

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?

Explicitly tells when to use: 'after building a feature, record the running app so it can be shared or read back.' Contrasts with CLI-only recording for real screen/window. Advises on prerequisites (Playwright, API key with ingest scope) and provides guidance on auth (storageState vs userDataDir). Also warns to check resolved source before proceeding.

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/manovagyanik1/clipy-mcp'

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