Skip to main content
Glama

The world according to capital

Update a bookmark

update_bookmark
Idempotent

Change a bookmark's fields; omitted fields keep their value. tag_groups merges by group: a group you send replaces that group, an empty list removes it, and groups you leave out are kept. new_slug renames it, and the old slug keeps resolving. Curator only.

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": {
      "slug": "<slug>"
    },
    "name": "update_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoWhere the bookmark points. ?ref=notacompany is added on the way out and stripped on the way in.
noteNoTiago's take: his one-line note on the bookmark.
slugYesThe bookmark to change.
batchNoAn accelerator batch as the accelerator spells it: "Summer 2026" (YC), "SR007" (a16z speedrun).
stageNo
titleNo
amountNoA raise's amount in USD cents.
hiddenNoHidden bookmarks stay approved but leave the public feed.
excerptNo
summaryNo
categoryNo
new_slugNoRename the bookmark's URL; the old slug becomes an alias.
cover_urlNoFound from the destination's og:image on approval when left out.
one_linerNoA company's name, a spaced em dash, and what it makes, for whom ("Peppermint — Billing and collections for clinical trial sites"); an issue prints it as the item's title, the name in bold, with the round under it. No amount, no investors. Written on approval when left blank.
source_urlNoThe article or announcement, when it differs from url.
tag_groupsNoTags in their display spelling ("Sands Capital", "$100M+"), grouped.
published_atNoISO 8601 date or datetime; defaults to now on create.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description's real contribution is the non-obvious merge rule for tag_groups (send replaces, empty list removes, omitted keeps) and the fact that a renamed slug keeps resolving as an alias. It also discloses the curator-only authorization requirement, which annotations do not cover. It stops short of saying what happens to approval state or the public feed when fields change.

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

Conciseness5/5

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

Four short sentences, front-loaded with the patch contract before the two special cases, and no filler. The terse "Curator only." fragment is efficient rather than sloppy.

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 17-parameter mutation with a nested object and no output schema, the description covers the contract (partial update), the two surprising parameters, and the authorization gate. It leaves unstated what the response contains and how hidden/approval state interacts with edits, which is a modest gap given the schema's own coverage.

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?

With 71% schema coverage across 17 parameters, the schema carries most of the load, but the description adds genuine meaning for the two hardest parameters: tag_groups' per-group merge semantics and new_slug's alias behavior. The remaining parameters (url, note, one_liner, cover_url) are already well described in the schema, so no further compensation is needed.

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?

"Change a bookmark's fields" is a specific verb+resource, and the patch semantics ("omitted fields keep their value") immediately separate it from create_bookmark or delete_bookmark. It never names a sibling explicitly, so differentiation is inferred from the verb rather than stated.

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?

"Curator only" establishes a prerequisite and the patch semantics imply when to use it (partial edits rather than full replacement), but there is no explicit statement of when to prefer this over create_bookmark or update_collection, and no guidance on error cases such as an unknown slug.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources