Skip to main content
Glama
Sign In
ArchiveBox API

ArchiveBox API

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Sync persona

archivebox_sync_persona

Create or update a browser persona from a browser extension export, including settings, cookies, and auth data for syncing owner-provided credentials.

Instructions

POST /api/v1/personas/sync

Create or update a browser persona from the browser extension's export. The cookies and auth data are credentials: only sync personas the owner provided.

Args: extension_persona_id: The extension's persona id. name: Persona name. settings: Browser settings. cookies_txt: Netscape cookies.txt content. auth_json: Auth/session storage export.

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": {
      "extension_persona_id": "<extension_persona_id>",
      "name": "<name>"
    },
    "name": "archivebox_sync_persona"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
settingsNo
auth_jsonNo
cookies_txtNo
extension_persona_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish this is a non-read-only, open-world, non-destructive mutation, and the description adds genuinely new context: the payload contains credentials (cookies and auth data) requiring owner consent. It does not disclose what an update overwrites on an existing persona, which is notable given idempotentHint=false on what reads as an upsert.

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 core sentence is front-loaded and the credential warning follows immediately, which is the right ordering. The leading 'POST /api/v1/personas/sync' line and the docstring-style Args block add mild redundancy, but nothing is egregiously wasteful.

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

Completeness3/5

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

For a credential-bearing mutation with no output schema, the description covers inputs and a safety caveat but leaves gaps: no return value description, no auth/permission requirements, no error or conflict behavior, and no clarification of what an 'update' replaces. Adequate to call correctly, incomplete for predicting outcomes.

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 coverage is 0%, so the Args block is doing the work, but it largely restates parameter names: 'name: Persona name', 'settings: Browser settings'. The format hints for cookies_txt ('Netscape cookies.txt content') and auth_json ('Auth/session storage export') do add real meaning, partially compensating for the coverage gap.

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?

States a specific verb and resource: 'Create or update a browser persona from the browser extension's export,' which tells an agent exactly what is created and from where. It is distinguishable from the only persona-related sibling, archivebox_get_personas, though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

Provides a real usage constraint ('only sync personas the owner provided') and implies the source is a browser-extension export, but gives no explicit when-to-use vs. when-not guidance relative to archivebox_get_personas or the archiving tools, and no prerequisites such as API token requirements.

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