Skip to main content
Glama
Sign In
ArchiveBox API

ArchiveBox API

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Browser session

archivebox_browser_session

Exchanges an administrator API key for a browser session cookie, enabling authenticated access to ArchiveBox web UI and file views.

Instructions

POST /api/v1/auth/browser_session

Exchange an administrator API key for a normal browser session (the response sets the session cookie used by the web UI and file views).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "archivebox_browser_session"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the description's job is to add context. It does: it discloses the POST endpoint, that an administrator API key is required, and that the call has the side effect of setting a session cookie. It omits session lifetime/expiry and whether an existing session is replaced, so it is not a 5.

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 short sentences, front-loaded with the action and followed by the effect, with no filler. The raw route string 'POST /api/v1/auth/browser_session' largely duplicates the tool name and consumes space a note about session lifetime would have used better.

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?

With no input schema properties and no output schema, the description must carry the whole burden, and it covers the auth requirement and the cookie side effect. It does not say what the response body contains or how an agent should reuse the cookie in subsequent calls, which is the key missing piece for a session-establishing tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not invent parameter detail for a parameterless call.

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 action and resource: exchange an administrator API key for a normal browser session. That is far more than a restatement of the name. It does not explicitly distinguish itself from the auth-adjacent sibling archivebox_get_api_token, so it falls short of a 5.

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?

The clause 'used by the web UI and file views' implies the situation in which the resulting session is needed, which is real but indirect guidance. There is no explicit when-to-use vs. when-not, no mention of prerequisites such as needing admin credentials first, and no named alternative for agents that only need API access.

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