Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram

Get the user a dedicated IP for sites that need one

lease_ip

Some sites (LinkedIn, marked 📍 in get_library) only accept a login from the address it signed in from. A dedicated IP is one address that only this account uses, and once the account holds one, every sign-in link and every later call on that login uses it automatically.

Call with no arguments first. If the account already holds one, it says so and nothing is bought. Otherwise it returns priceCents and a message with the price for termDays days in country (default US). The price is charged up front and is not refundable. If something must happen first (a card on file, a one-time identity check), mustFirst names it with the link that fixes it: give your user that link and stop.

Never buy without asking. Tell your user the exact price and buy only if they agree, by calling again with confirmPriceCents set to the price they agreed to. A live price above that is refused before any charge, and repeating the same call cannot buy two. Pass another: true only when your user asked for a second IP.

Input Schema

Name	Required	Description
`another`	No	Buy a second IP although the account holds one. Only when your user asked.
`country`	No	Two-letter country code for the IP, e.g. "US" (the default).
`termDays`	No	How many days the IP is held, paid up front (default 30).
`confirmPriceCents`	No	The price in US cents your user agreed to, from the unconfirmed call. Only this buys.

Output Schema

Name	Required	Description
`error`	No	Why it failed, when it did.
`status`	No	The HTTP status of the lease: below 400 succeeded.
`message`	No	What happened, in words.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "error": {
+      "description": "Why it failed, when it did."
+    },
+    "message": {
+      "description": "What happened, in words.",
+      "type": "string"
+    },
+    "status": {
+      "description": "The HTTP status of the lease: below 400 succeeded.",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

AddedOct 17, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The annotations only declare non-read-only, non-idempotent, non-destructive, closed-world; the description adds the critical behavior the annotations do not: cost is charged up front, is non-refundable, a live price above the agreed figure is refused before any charge, and repeated identical calls cannot double-buy. It also discloses the prerequisite path via `mustFirst`. It stops short of describing what the granted IP looks like on success, though the output schema covers that.

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 the why (which sites need it) before the how, and the bolded 'Never buy without asking' rule is easy to find. A few sentences are longer than needed (the opening explanation of what a dedicated IP is), but nothing is redundant.

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 paid, two-phase mutation tool, the description covers the decision path, the safety gate, the prerequisite escape hatch, and the cost model, and an output schema exists so return shape need not be restated. An agent has everything needed to call it safely.

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?

Schema coverage is 100% so the baseline is 3, but the description adds real meaning beyond the schema: `confirmPriceCents` is the only parameter that actually triggers a purchase and must match the user-agreed price, while `another` is gated on explicit user request. It does not add detail on `country` or `termDays` beyond the schema, which already carries defaults.

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 (lease/buy) and resource (a dedicated IP) and immediately explains the motivating scenario: sites like LinkedIn marked 📍 in `get_library` that only accept sign-ins from the original address. An agent can distinguish this from sibling tools such as get_library or add_connection without opening any 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 call sequence: call with no arguments first to get a price, then call again with `confirmPriceCents` to buy. It also names the exclusion for `another: true` (only when the user asked for a second IP) and the fallback when `mustFirst` is set (give the user the link and stop).

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

All Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.