Skip to main content
Glama

The world according to capital

Reject bookmarks

reject_bookmarks
Idempotent

Reject up to 100 bookmarks by slug, all with the same optional reason; send one call per reason. They stay stored and can be approved later. 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": "reject_bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes
rejection_reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: rejected bookmarks remain stored, the operation is all-or-nothing, missing slugs are named in the error, and the 100-slug limit applies. It also confirms the curator permission requirement, which is essential for correct invocation.

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 tight sentences, front-loaded with the action and batch limit, followed by persistence, atomicity, and permission details. No sentence is redundant.

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 batch mutation tool with no output schema, it covers the critical behaviors an agent needs: permission scope, batch size, reason grouping, persistence, atomicity, and error behavior. Nothing essential is missing.

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 0% schema description coverage, the description compensates well by explaining that slugs identify bookmarks and that one optional reason applies to the whole batch. It does not define slug formatting, but the operational meaning is otherwise clear.

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?

States a specific verb and resource (reject bookmarks by slug), including the batch size and shared-reason scope. It clearly distinguishes the operation from approving and is understandable without opening the schema.

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

Usage Guidelines4/5

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

Provides clear operational context: curator-only access, one call per reason, and the note that bookmarks may later be approved. It does not explicitly name approve_bookmarks as the alternative, but the use case and constraints are clear.

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