Skip to main content
Glama

The world according to capital

List bookmarks

list_bookmarks
Read-only

List bookmarks, newest first: filter by category, tag, source, or date. A curator may pass status to list pending or rejected ones.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
tagNoA tag's slug or any of its spellings.
dateNo
fromNo
pageNo
limitNo
queryNo
sourceNo
statusNopending or rejected need a curator.
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world behavior, so the description earns credit for adding the default sort order (newest first) and the curator-only constraint on status filters. It omits pagination defaults and what the response looks like, but those are partially covered by the schema.

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?

Two compact sentences with the primary behavior first and the curator caveat second. Nothing is redundant and no filler is present.

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 10-parameter read tool with no output schema and low schema coverage, the description leaves meaningful gaps: the query parameter is unexplained, the from/to date range is collapsed into 'date', pagination behavior is unstated, and the return shape is not characterized.

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 only 20% schema description coverage, the description must compensate, and it does name category, tag, source, date and status as filters. However, query, from/to range semantics, page and limit are left entirely to the schema, so half the parameters get no added meaning.

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+resource (list bookmarks) plus the inherent ordering (newest first) and the available filter dimensions. It does not name the closely overlapping sibling list_pending_bookmarks, so the agent must infer the boundary itself.

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 implied through the filter list and the note that a curator may pass status to see pending or rejected bookmarks, which usefully flags a permission prerequisite. There is no explicit when-not guidance and no routing to list_pending_bookmarks, which appears to cover the pending-only case.

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