Skip to main content
Glama
usewrit

writ-mcp

Official
by usewrit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Record a website task

writ_record_website
Destructive

Record repeatable website tasks as workflows that replay on demand. Capture browser actions to automate and repeat site interactions without AI cost.

Instructions

Record a repeatable website TASK as a workflow that replays on demand. Use whenever the user asks to record, capture, teach, automate or repeat actions on a site and the point is the TASK, not an API surface. Writ opens a real cloud browser and returns an observation; YOU are the brain: drive it with writ_browser_act, author what the recorder cannot see with writ_browser_compose (inputs a caller passes, explicit steps, named functions), and call writ_browser_save when the goal is complete — the saved workflow then replays at zero AI cost (writ_run_workflow, or its own run_ tool once pinned with writ_pin_workflow_tool) and can be scheduled. A goal that asks for an API ("turn into an API", "an endpoint for") is routed to writ_website_to_api's intelligent ladder automatically (static crawl, rendered crawl, then Writ's AI browser rung), so the recording is a real build. Before anything runs it proposes the user's OWN matching workflows (existing_workflows) and ready-made marketplace APIs (marketplace_candidates); skip_existing / skip_marketplace bypass those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesWebsite URL to start on (required).
goalYesWhat should be recorded on the website, in plain language
deviceNoA linked Writ desktop's agent_id (writ_devices): act ON it. Omit to use the desktop this connection chose with writ_devices action='use' (if any).
persona_idNoSaved identity to sign in with (list them with writ_personas). Required for sites behind a login with 2FA — the one-time code is then minted server-side and never shown to you. A desktop persona ('device:…') records on its own desktop, which fills its values itself.
skip_existingNoAPI builds first propose the user's OWN matching workflows (replaying is instant and free); set true after the user declined those.
use_residentialNoOpen on the platform residential network (premium) for a site that blocks datacenter IPs or shows a bot wall. Default off (free datacenter egress).
skip_marketplaceNoAPI builds then propose compatible ready-made marketplace APIs; set true to skip that and record fresh.
residential_countryNoTwo-letter ISO country the residential exit should be in (e.g. 'us', 'fr') — for a site that serves a different page per country, or throttles foreign traffic. Omit for an automatic exit. Ignored unless the session egresses residential.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: it opens a real cloud browser and returns an observation, the agent must drive it via writ_browser_act/compose/save, the saved workflow replays at zero AI cost and can be scheduled, and it proposes existing_workflows/marketplace_candidates before running. It does not explain the destructiveHint=true implications or permission/auth needs, which keeps it short of a 5 against already-rich annotations.

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?

Front-loads purpose in sentence one and each following sentence carries routing or workflow information. It is dense and long with heavy parenthetical content referencing many sibling tools, which costs some readability, but little of it is padding.

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?

For a complex 8-parameter, open-world, non-idempotent recording tool with no output schema, the description covers the trigger, the alternatives, the multi-tool authoring flow and the bypass flags. It stops short of describing the return/observation shape or failure behavior, but is complete enough to invoke correctly.

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 schema already documents all 8 parameters, making 3 the baseline. The description adds only marginal meaning (the skip_existing/skip_marketplace bypass rationale) and no extra syntax or format detail 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?

Opens with a specific verb+resource: 'Record a repeatable website TASK as a workflow that replays on demand.' It explicitly distinguishes this tool from the sibling writ_website_to_api by stating API-shaped goals are routed there automatically, so an agent can tell them apart without opening a schema.

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?

Gives an explicit trigger ('whenever the user asks to record, capture, teach, automate or repeat actions on a site and the point is the TASK'), names the alternative and the condition that selects it (API goals -> writ_website_to_api), and sketches the in-tool flow (act/compose/save) plus skip_existing/skip_marketplace bypass semantics.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools