Skip to main content
Glama

Save bookmark

save_bookmark

Save a link with a title, optional notes, and tags to a personal SQLite knowledge base for later search and retrieval.

Instructions

Save a link with a title and optional notes.

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>",
      "title": "<title>"
    },
    "name": "save_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttp(s) URL to save
tagsNo
notesNoWhy it's worth keeping
titleYes

Output Schema

NameRequiredDescriptionDefault
idYes
uriYesResource URI for this note
urlNoSet for bookmarks
bodyYes
tagsYes
titleYes
created_atYes
updated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-destructive, closed-world, non-idempotent write, so the safety profile is covered elsewhere. The description adds nothing beyond that — no duplicate handling, no mention that tags exist as a second optional field, no error or validation behavior. For a simple create-style tool the bar is low, so a 3 is fair but there is essentially no added behavioral context.

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?

A single front-loaded sentence with no filler, which is appropriate in size. It is concise to the point of omitting the tags parameter, so brevity costs some completeness rather than being pure efficiency.

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?

Low-complexity tool with an output schema (returns need no explanation) and annotations covering the safety profile, so the essentials are present. The gaps — undocumented tags semantics and no guidance on duplicates or when to use this versus add_note — are minor but real for a save/mutation operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% (url and notes are documented; title and tags are not), so the description needed to compensate and largely does not. It maps 'link', 'title', and 'optional notes' onto three of the four params but omits tags entirely — the one undocumented repeatable field an agent would most need help with (purpose, limits, format).

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 verb and resource: saving a link (bookmark) with a title and optional notes. That is clear enough for an agent to know the operation, though it never contrasts with add_note or explains whether a bookmark is distinct from a note, leaving sibling differentiation implicit.

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?

Usage is only implied by the verb 'save' — the agent can infer this is the tool for capturing a URL, but there is no statement of when to prefer it over add_note, no prerequisites, and no mention of what happens on re-saving the same link. Annotation idempotentHint=false suggests duplicates are possible, but the description never addresses it.

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