Skip to main content
Glama

add_private_bookmark

Save private, URL-less content to Instapaper for personal notes, clipped text, emails, or Slack messages. Provide HTML content and a source label to keep bookmarks organized.

Instructions

Save private content without a URL to Instapaper (e.g., from emails, notebooks, clipped text, Slack messages). Private bookmarks are not shared and don't have URLs. Perfect for personal notes, clipped content, or information from sources without URLs. Requires HTML content to be provided.

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": {
      "content": "<content>",
      "source_label": "<source_label>"
    },
    "name": "add_private_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoOptional title for the bookmark
contentYesHTML content of the private bookmark. Can be plain text or HTML.
folder_idNoOptional folder ID to save the bookmark in
descriptionNoOptional description or notes
source_labelYesSource label for this private bookmark (e.g., "email", "notebook", "slack", "clipped-text")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: bookmarks are private, not shared, and have no URL. It omits what happens after saving (return value, duplicate handling, default folder) and adds a slightly misleading constraint, "Requires HTML content to be provided," while the schema says plain text is also accepted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the next two sentences restate the same ideas: "without a URL" is repeated twice more and the use-case list duplicates the examples. Roughly a third of the text could be removed without losing information.

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 mutation tool with no annotations and no output schema, the description covers purpose, privacy semantics, and the required content input. It leaves open the result of the call, default folder behavior, and the source_label value set that the schema does not constrain with an enum.

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 five parameters are already documented, including source_label examples, making the description's list of sources largely redundant. The one additive point is calling out that content is required, though the "HTML content" phrasing conflicts with the schema's "Can be plain text or HTML."

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 states a specific verb and resource ("Save private content ... to Instapaper") and carves out a clear scope: content without a URL, kept private. That scope implicitly separates it from the URL-based add_bookmark sibling, but the alternative tool is never named, so an agent must infer which sibling handles URL bookmarks.

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?

It gives concrete when-to-use context ("e.g., from emails, notebooks, clipped text, Slack messages") and states the selecting condition ("without a URL"). It stops short of an explicit routing rule such as "use add_bookmark when you do have a URL," so an agent still has to derive the branch from the sibling names.

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