Skip to main content
Glama

add_bookmark

Save an article or web page URL to Instapaper for later reading. Returns the bookmark ID, title, and URL, and accepts optional title, notes, and folder ID to organize the saved item.

Instructions

Save an article or web page to Instapaper. Use this when the user wants to save a URL for later reading. Returns the bookmark ID, title, and URL. You can optionally provide a title, description/notes, and a folder ID to organize the article.

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": {
      "url": "<url>"
    },
    "name": "add_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL of the article to save
titleNoOptional title for the bookmark
folder_idNoOptional folder ID to save the bookmark in
descriptionNoOptional description or notes about the article

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does disclose the return payload (bookmark ID, title, URL), which is genuinely useful since there is no output schema. It says nothing about duplicate URLs, auth requirements, or whether the save is idempotent, which matters for a write 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?

The purpose sentence is front-loaded and the rest is compact. The phrasing "Save an article or web page" followed by "save a URL for later reading" partially repeats the same idea, a minor redundancy.

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

Completeness4/5

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

For a single-required-URL tool with flat parameters, the description covers purpose, when to call it, the optional inputs, and the return values that the absent output schema would otherwise provide. Only the write-side edge cases are missing.

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 100%, so all four parameters are already documented in the schema. The description echoes the same fields (title, description/notes, folder ID) without adding format, constraints, or interaction rules, so the baseline of 3 applies.

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?

The description uses a specific verb+resource ("Save an article or web page to Instapaper") rather than restating the name, so the action is unambiguous. It also enumerates the optional fields. It does not distinguish itself from the sibling add_private_bookmark, leaving the agent to infer the difference.

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?

"Use this when the user wants to save a URL for later reading" gives an explicit triggering condition. There is no when-not guidance and no named alternative for saving privately, which keeps it short of a 5.

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