Skip to main content
Glama
Sign In

Curated

by network.curated
OverviewDiscussionsAdmin

Edit a list

update_list
DestructiveIdempotent

Edit a list's title, subtitle, or category. Saves the working version without publishing. Readers keep seeing the last approved version until the owner approves a list update.

Input Schema

NameRequiredDescriptionDefault
listYesWhich list: slug, exact title, or id. Must match exactly one list or the call fails.
titleNoNew title.
categoryNoThe category the person chose: Food & Drink, Travel, Books, Music, Movies & TV, Gear & Tools, Software, Fashion, Home & Garden, Ideas & Essays, Art, or Spirituality. Their choice stays; an empty string clears it.
subtitleNoNew subtitle. Pass an empty string to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / category / maxLength
      Added value: +60
    • addedInput schema / properties / subtitle / maxLength
      Added value: +200
    • addedInput schema / properties / title / maxLength
      Added value: +120
  2. Changed1 schema field changed
    • removedInput schema / properties / about
      Removed value: -{
-  "additionalProperties": false,
-  "description": "The curator's own words about this list. Ask for their answer; do not write personal experience for them.",
-  "properties": {
-    "how": {
-      "description": "The rule for what makes the cut.",
-      "maxLength": 1200,
-      "type": "string"
-    },
-    "who": {
-      "description": "Who the list is and is not for.",
-      "maxLength": 1200,
-      "type": "string"
-    },
-    "why": {
-      "description": "What started this list.",
-      "maxLength": 1200,
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag this as a non-readonly, idempotent, destructive write; the description adds genuinely new context by explaining that changes land in a working version and readers still see the last approved version until approval. It does not disclose that fields can be wiped via empty strings (the destructive surface), which the schema alone conveys, so it falls just short of full transparency.

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 short sentences, front-loaded with the action and followed by the two behavioral facts that matter. Nothing is padded and no sentence restates the title or annotations verbatim.

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?

With full schema coverage, annotations, and no output schema, the description covers what an agent needs to call it correctly and what happens to readers. It omits the clearing/overwrite behavior and any permission or ownership prerequisite implied by "the owner approves," leaving a small gap for a mutation tool.

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?

Schema description coverage is 100%, so every parameter including the list selector, max lengths, and empty-string clearing is already documented inline. The description names the editable fields but adds no format, matching, or clearing semantics beyond the schema, so the baseline 3 applies.

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 the exact editable fields ("Edit a list's title, subtitle, or category"), so the agent knows precisely what mutation scope to expect. "Saves the working version without publishing" separates it from publish_list and update_item without naming them ambiguously.

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?

The draft-vs-approved sentence gives a clear condition for using this tool rather than publishing: edits go to a working version and only reach readers after owner approval. It stops short of explicitly naming publish_list or update_item as the alternative, so 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.

All Curated toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources