Skip to main content
Glama

The world according to capital

List collections

list_collections
Read-only

List the pages that list bookmarks (YC batches, speedrun cohorts, /startups pages), each with its rule, its copy and how many bookmarks it holds. Public callers see published pages; a curator sees drafts and retired pages too, with status, target_query and a preview_url for each page not yet published.

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_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
statusNodraft or retired need a curator.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint/openWorldHint already covering the safety profile, the description adds real behavioral context: it discloses that results include each page's rule, copy, and bookmark count, and that curators additionally see drafts, retired pages, status, target_query, and preview_url. It does not mention result ordering or volume limits, so it is strong but not exhaustive.

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 tight sentences: the scope and return contents come first, then the permission-dependent visibility delta. Every clause carries information an agent would otherwise have to guess, and nothing is repeated from the schema or annotations.

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

Completeness4/5

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

The tool has no output schema, and the description steps in to describe the returned fields and the curator-only extras, which is the right allocation of effort for a two-optional-parameter list tool. Only ordering/pagination and the meaning of the 'category' kind value are left unaddressed.

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?

Schema coverage is 50%, with kind carrying only an enum and status carrying a brief note. The description compensates by grounding the kind values in recognizable concepts (batches, cohorts, startups pages) and by restating the curator gate for draft/retired status in behavioral terms. It adds meaningful context but does not fully enumerate what each enum value returns.

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?

The description gives a clear verb and resource ("list the pages that list bookmarks") and disambiguates the resource by naming concrete examples (YC batches, speedrun cohorts, /startups pages), which separates it from list_bookmarks. It stops short of explicitly naming a sibling tool or stating what it is not, so it lands just under a 5.

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 rather than stated: the public-vs-curator visibility split tells an agent what it will get, but not when to choose this tool over list_bookmarks or list_pending_bookmarks. There are no explicit exclusions or preconditions beyond the curator note that already appears in the status parameter.

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