Skip to main content
Glama

The world according to capital

Create a bookmark

create_bookmark

Create a bookmark. It starts pending; approve it to publish. Needs a title and a url or source_url. The slug is derived from the title unless given. 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": {
      "title": "<title>"
    },
    "name": "create_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.
batchNoAn accelerator batch as the accelerator spells it: "Summer 2026" (YC), "SR007" (a16z speedrun).
stageNo
titleYes
amountNoA raise's amount in USD cents.
hiddenNoHidden bookmarks stay approved but leave the public feed.
excerptNo
summaryNo
categoryNo
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

B3.4/5.0
Behavior3/5

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

Annotations already flag a non-read-only, non-idempotent, non-destructive write. The description adds genuinely useful behavior beyond them: the record starts pending, must be approved to appear, and the slug is derived from the title when omitted. It still says nothing about what happens to the many optional fields, validation failures, or whether duplicates are rejected.

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?

Four short sentences, front-loaded with the action and followed by lifecycle, required input, and permission. Efficient overall, though the 'Needs a title and a url or source_url' line is imprecise enough to mislead rather than save space.

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 15-parameter create tool with nested tag_groups and no output schema, the description covers the essentials (required input, lifecycle, slug, permissions) but leaves most optional fields and the returned object unaddressed. Adequate to call correctly, thin for calling well.

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?

With 67% schema coverage on 15 parameters, the schema carries most of the meaning. The description adds the title-to-slug derivation and the url/source_url relationship, but says nothing about batch, stage, category, tag_groups, hidden, or the note/excerpt/summary distinctions.

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?

Opens with a specific verb+resource ('Create a bookmark') and adds the lifecycle fact that it starts pending, which separates it from approve_bookmarks and update_bookmark. It stops short of naming a sibling explicitly, so an agent must infer the create-vs-update boundary.

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' gives a real prerequisite, and 'approve it to publish' points at the approval path. However, 'Needs a title and a url or source_url' conflicts with the schema, which requires only title, leaving the agent unsure whether url is mandatory.

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