Skip to main content
Glama

The world according to capital

Draft a collection

create_collection

Draft a new collection page. It is always a draft, seen only at its preview_url until publish_collection. kind is yc_batch (rule {batch: "Fall 2026"}), speedrun_cohort (rule {batch: "SR008"}), startups (rule {tags: [slug, ...], category?}, any of the tags, or {stage: "series_b", category?}, every round at that stage: one of pre_seed, seed, series_a, series_b, series_c, series_d, growth; tags and stage never go together) or category (rule {category: value}; every category already has one). Every page is served at /collections/{slug}; slug is the words people search for it by ("yc-fall-2026", "robotics-startups"), unique across collections. A startups or category page needs its own title, h1, lead and description; a batch or cohort may leave them blank for its template. {count}, {first} and {latest} fill in, and {batch} on a batch. target_query is the one search the page is written for, unique across collections. controls says what the page offers over its cards: search (true/false), filters (any of topic, investor, stage), sorts (one or more of newest, biggest, the page's own order first) and group (day or none); a key left out keeps its default ({"search":false,"filters":[],"sorts":["newest","biggest"],"group":"none"}). 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": {
      "kind": "<kind>",
      "slug": "<slug>",
      "rule": "<rule>"
    },
    "name": "create_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
h1No
kindYes
leadNo
ruleYes
slugYesThe page's address, /collections/{slug}: lowercase words joined by hyphens, as people search for it ("yc-fall-2026", "a16z-speedrun-sr008", "defense-tech-startups").
titleNoThe search title, ending " | notacompany".
promiseNo
controlsNoWhat the page offers over its cards; a key left out keeps its default.
descriptionNoThe meta description, at most 160 characters.
target_queryNoThe one search this page is written for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare write/non-destructive/non-idempotent/non-open-world; the description adds substantially more: the page is always a draft visible only at preview_url, it requires curator privileges, slug and target_query are unique across collections, and omitted controls keys fall back to documented defaults. These are exactly the side effects and constraints an agent needs before invoking a mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key fact (draft until publish) is front-loaded and little is pure filler, but the body is one dense paragraph of nested parentheticals covering four kinds, rule variants, template placeholders and a controls default in a single run-on block. It is information-rich but hard to scan, and the controls-default sentence duplicates the schema's own description.

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?

For a 10-parameter mutation with a nested rule object, no output schema and half the schema undescribed, the definition covers nearly everything: validation constraints, defaults, conditional field requirements, and the preview_url return location. The unexplained `promise` parameter and absent error behavior (e.g., on a duplicate slug) are the only material omissions.

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 only 50% schema coverage, the description carries real weight: it explains the kind/rule combinations (tags XOR stage, batch for yc_batch and speedrun_cohort), the slug convention, the target_query uniqueness, which fields a batch page may leave blank, and the controls default object. The gap is `promise`, which appears in the schema with no description here, and the sorts phrasing ("the page's own order first") is hard to parse.

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?

"Draft a new collection page" gives a specific verb and resource, and the body immediately scopes it as a draft-only operation distinct from publish_collection and (by implication of "new") update_collection. An agent can identify the operation and its lifecycle position without opening any 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?

It names the follow-up tool explicitly ("until publish_collection") and states the audience restriction ("Curator only"), which tells the agent when this is the right call. It does not explicitly say when to use update_collection instead of creating a new page, so the alternative-routing is implied rather than spelled out.

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