Skip to main content
Glama
ContextBolt

ContextBolt Bookmarks

Official

save_bookmark

When chatting, store a URL and content in your ContextBolt collection with optional tags for later semantic search.

Instructions

Save a new bookmark to your ContextBolt collection while chatting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the page or post to save.
contentYesMain text content to index.
titleNoOptional title.
authorNoOptional author or handle.
tagsNoOptional tags.
Behavior2/5

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

No annotations provided, so description bears full burden. It only says 'save a new bookmark', but does not disclose potential side effects (e.g., duplication, required authentication) or behavior details.

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?

Single, front-loaded sentence with no wasted words.

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

Completeness2/5

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

Given 5 parameters (2 required) and no output schema, the description is too sparse. It does not explain return format, error handling, or post-save behavior, which would help an agent anticipate outcomes.

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 description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the parameter descriptions already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'save' and resource 'bookmark', and distinguishes itself from siblings like search_bookmarks or get_recent_bookmarks by specifying the context 'while chatting'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., search_bookmarks). Does not mention exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ContextBolt/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server