Skip to main content
Glama

Record a website task

writ_record_website
Destructive

Records a repeatable task on a site as a workflow (goal + start url): the same session as writ_browser_use, labelled with its goal, driven with writ_browser_act and saved with writ_browser_save. A goal that asks for an API opens as a writ_website_to_api build instead: the same browser, bound to the build.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "goal": "<goal>",
      "url": "<url>"
    },
    "name": "writ_record_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
goalYes
deviceNo
auth_modeNo
fresh_exitNo
persona_idNo
skip_existingNo
use_residentialNoResidential exit (bot walls, another country). Omitted: Writ's residential list decides. Pair with residential_country.
skip_marketplaceNo
residential_countryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / auth_mode
      Added value: +{
      +  "enum": [
      +    "reuse",
      +    "fresh_login"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / device
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / fresh_exit
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / residential_country
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / skip_existing
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / skip_marketplace
      Added value: +{
      +  "type": "boolean"
      +}
    • changedInput schema / properties / use_residential / description
      Previous value: -"Residential network (bot walls)."New value: +"Residential exit (bot walls, another country). Omitted: Writ's residential list decides. Pair with residential_country."
  2. Changed11 schema fields changed
    • removedInput schema / properties / auth_mode
      Removed value: -{
      -  "description": "Browser recordings only: reuse verifies unknown saved auth before adoption; fresh_login records a new login without restoring old cookies, headers or storage. Device identity stays the same.",
      -  "enum": [
      -    "reuse",
      -    "fresh_login"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / device
      Removed value: -{
      -  "description": "A linked Writ desktop's agent_id (writ_devices) to act on. Omitted: the desktop this connection chose with writ_devices action='use', if any.",
      -  "type": "string"
      -}
    • removedInput schema / properties / fresh_exit
      Removed value: -{
      -  "description": "Residential only: skip the persona's usual exit for this site and draw a new address — after the site refused it (an IP rate limit, a sign-in rejected with correct credentials). Ignored on server-IP egress.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / goal / description
      Removed value: -"What should be recorded on the website, in plain language"
    • removedInput schema / properties / human_layer
      Removed value: -{
      -  "description": "Browser recordings only: native keyboard input, distance-adaptive mouse paths and pre-click dwell. Fresh login enables it by default; false explicitly disables it. Native actionability checks remain active.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / persona_id / description
      Removed value: -"Saved 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 the caller. A desktop persona ('device:…') records on its own desktop, which fills its values itself."
    • removedInput schema / properties / residential_country
      Removed value: -{
      -  "description": "Two-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.",
      -  "type": "string"
      -}
    • removedInput schema / properties / skip_existing
      Removed value: -{
      -  "description": "API builds first propose the user's OWN matching workflows (replaying is instant and free); set true after the user declined those.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / skip_marketplace
      Removed value: -{
      -  "description": "API builds then propose compatible ready-made marketplace APIs; set true to skip that and record fresh.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / url / description
      Removed value: -"Website URL to start on (required)."
    • changedInput schema / properties / use_residential / description
      Previous value: -"Open on the platform residential network (premium) for a site that blocks datacenter IPs or shows a bot wall. Default off (free datacenter egress)."New value: +"Residential network (bot walls)."
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, so the safety profile is known. The description adds genuine behavioral context beyond that by framing the result as a labelled session workflow driven by writ_browser_act and persisted by writ_browser_save. It still does not say what is actually destroyed by a repeat run, whether a session is created immediately, or what happens with the eight optional parameters.

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?

Two dense sentences with no filler, and the core definition is front-loaded before the sibling routing and the API alternative. The second sentence's closing phrase 'bound to the build' is terse to the point of being cryptic, which costs a little clarity.

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?

For a destructive, non-idempotent, open-world tool with 10 parameters at 10% description coverage and no output schema, the description answers what and roughly when but not how the optional parameters change behavior or what is returned. An agent cannot safely choose auth_mode, fresh_exit or persona_id from what is written here.

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

Parameters2/5

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

Schema description coverage is only 10% across 10 parameters, so the description carries the burden of explanation, and it explains only the two required ones — goal and url, including the special semantics of a goal that requests an API. It says nothing about device, auth_mode, fresh_exit, persona_id, skip_existing, use_residential, skip_marketplace or residential_country, leaving most of the surface undocumented in both places.

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?

States a specific verb and resource — 'Records a repeatable task on a site as a workflow (goal + start url)' — which tells an agent exactly what is produced (a saved workflow) from the required inputs. It also names writ_website_to_api and the condition that selects it, so the tool is distinguishable from its closest sibling without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: a goal that 'asks for an API' should go to writ_website_to_api instead, and it places the recording in a lifecycle chain with writ_browser_use, writ_browser_act and writ_browser_save. What's missing is any exclusion relative to other creation paths (e.g. automations, monitors, crawls), so the guidance is strong but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.