Skip to main content
Glama

The world according to capital

Revise a draft collection

update_collection
Idempotent

Change a draft collection's rule, copy, controls or target_query; omitted fields keep their value, and an empty string clears a field back to its template. A published page's words and controls are changed in Avo. 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>"
    },
    "name": "update_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
h1No
kindYes
leadNo
ruleNo
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 the generic safety profile (non-read-only, idempotent, non-destructive); the description adds genuinely new behavior: omitted fields retain their value (partial update), an empty string resets a field to its template, and the operation is restricted to curators and drafts. These are exactly the semantics an agent could get wrong without them.

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?

Three clauses, front-loaded with what is changed, then the update semantics, then the scope restriction. No filler and no repetition of the title 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?

For a 10-parameter mutation with nested objects and no output schema, the description covers the essentials: what is mutable, partial-update and clearing semantics, draft-only scope, and curator authorization. It leaves open minor edge cases such as whether kind can be changed for an existing slug and what happens to derived page content when rule changes.

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 50% schema description coverage across 10 parameters, several fields (h1, lead, promise, kind, the rule.category enum) are unexplained in either place. The description contributes useful cross-cutting semantics — omission preserves, empty string clears — but does not add per-parameter meaning beyond the schema's own descriptions of slug, title, description, rule, and controls.

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?

Uses a specific verb ("Change") on a specific resource ("a draft collection") and enumerates the editable surface (rule, copy, controls, target_query). It also draws an explicit line between draft collections handled here and published pages handled in Avo, so an agent can tell this apart from create_collection or publish_collection.

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?

Gives a clear when-to-use condition (draft collections) and a when-not (a published page's words and controls are changed in Avo), plus a prerequisite (Curator only). It stops short of naming a sibling tool as the alternative, but the exclusion is unambiguous.

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