Skip to main content
Glama

mcp-server

by me.ceki
OverviewDiscussionsAdmin

Rent Browser

rent-browser

[Auth Required + Active] Get credentials to rent a real Chrome browser. Install CLI: pip install ceki-sdk (Python) or npm install -g @ceki/sdk (Node). Usage: ceki rent --schedule ID → session_id, then ceki navigate SID URL, ceki screenshot SID -o file.png, ceki stop SID. Per-minute billing from AgentWallet. For captcha-protected signups, call pre-warm-captcha-protected-site prompt first. Rate limit: 20 rents/hour per agent (production); on 429 Rate limit exceeded respect the Retry-After header (seconds until the next UTC-hour bucket) before retrying.

Input Schema

NameRequiredDescriptionDefault
browser_idNoProvider browser ID from search-browsers results
subscription_idNoOwner CloudBrowser subscription ID (from /agent/browsers → subscriptions[]). Rents a free browser of that group at $0/min (owner already paid). Takes precedence over browser_id when both given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / browser_id / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • addedInput schema / properties / subscription_id
      Added value: +{
+  "description": "Owner CloudBrowser subscription ID (from /agent/browsers → subscriptions[]). Rents a free browser of that group at $0/min (owner already paid). Takes precedence over browser_id when both given.",
+  "minimum": 1,
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • removedInput schema / required
      Removed value: -[
-  "browser_id"
-]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: [Auth Required + Active] status, per-minute billing from AgentWallet, a rate limit (20 rents/hour), and exact 429/Retry-After semantics. It also sketches the session lifecycle (session_id, navigate, screenshot, stop), which is rich behavioral context for a rental operation.

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-loaded with auth status and purpose, then dense operational detail (install, usage, billing, rate limits). Every clause is arguably useful to an agent, though the CLI install commands are borderline padding for a tool-invocation context.

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?

For a two-parameter tool with no output schema and no annotations, the description covers auth, billing, rate limiting, retry behavior, and the post-rent workflow, so an agent has what it needs to call it correctly and handle failures.

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 both browser_id and subscription_id are already documented with precedence rules, and a baseline of 3 is appropriate. The description adds a usage example with `--schedule ID`, which does not map cleanly to either declared parameter and adds little meaning 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?

States a specific verb and resource ('Get credentials to rent a real Chrome browser'), immediately distinguishing it from siblings like search-browsers, list-my-browsers, and create-browser-subscription. An agent knows this is the rent action, not a search or a subscription-management call.

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 a concrete usage workflow and a conditional route: call pre-warm-captcha-protected-site first for captcha-protected signups. It does not, however, explicitly tell the agent to obtain browser_id from search-browsers or contrast this tool with create-browser-subscription / vault-clone-session, so sibling selection is left partly to inference.

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

All mcp-server toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources