Skip to main content
Glama

The world according to capital

Approve bookmarks

approve_bookmarks
Idempotent

Approve up to 100 bookmarks by slug and publish them. Approving a rejected bookmark restores it. All or nothing: if any slug is not found, nothing changes and the error names the missing slugs. 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": {
      "slugs": "<slugs>"
    },
    "name": "approve_bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior, yet the description adds substantive context the annotations cannot express: approving a previously rejected bookmark restores it, the operation is atomic ('all or nothing'), and the error names missing slugs. It also flags the curator-only permission requirement, which is critical for an agent to know before calling.

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 action and scope, then restoration behavior, then atomicity, then the permission gate. Every sentence carries information an agent needs; nothing is redundant with the title or schema.

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

Completeness5/5

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

For a single-parameter batch mutation with no output schema, the description covers the important unknowns: partial-failure semantics, error reporting on missing slugs, the effect on previously rejected items, and the authorization requirement. An agent has enough to call it correctly and to anticipate failure modes.

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?

The schema only says 'array of strings, 1-100'; the description clarifies that each string is a slug identifying a bookmark and reinforces the 100-item ceiling in prose. It also explains the consequence of an unresolvable slug, which is behavior the schema cannot convey, though it does not discuss slug format or case sensitivity.

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 gives a specific verb (approve), a specific resource (bookmarks, by slug), a bounded scope (up to 100), and the concrete outcome (publish them). The bookmark-scoped wording separates it from publish_collection, and 'approve' vs the reject_bookmarks sibling is unambiguous.

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 itself; there is no explicit statement of when to choose this over reject_bookmarks or list_pending_bookmarks, nor any prerequisite beyond 'Curator only'. The 'Curator only' note is a real access constraint, but it is a permission gate rather than when-to-use guidance.

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