Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Add several items to a collection

add_collection_items

Save up to 50 items into one existing collection in a single step — typically the drafts from draft_collection_items that the user kept. They are saved as DRAFTS by default and stay hidden from visitors. Set status to "published" only after the user explicitly asks for it; each published item is sent to the public site by collection auto-publish, so confirm that public change before calling. Each item is saved on its own, so one bad item never blocks the rest; the result lists any that failed.

Input Schema

NameRequiredDescriptionDefault
itemsYesThe items to save (1-50), e.g. the drafts the user kept.
statusNoOmit to save them all as DRAFTS. "published" only on an explicit instruction to go live.
site_idYesThe site the collection belongs to
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
collection_typeYesThe collection's slug, as list_collections returns it (e.g. "blog", "menu", "products", "faqs").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only flag it as a non-idempotent, open-world, non-destructive write. The description adds substantive behavior: items are hidden from visitors unless published, published items are pushed live by collection auto-publish, and saves are per-item so a single bad item does not abort the batch. It even characterizes the result (the list of failures) despite there being no output schema.

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 dense sentences with the default behavior, the risky deviation, the safety precondition, and the failure model — each earning its place, with the safe default front-loaded ahead of the publishing caveat.

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 5-parameter batch write with no output schema, the description covers everything an agent needs: input source, default vs. published outcome, the confirmation gate for public changes, partial-failure semantics, and what the response reports. Nothing material is left to inference.

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 the schema already documents site_id, collection_type, status, items and user_goal. The description's notes on status defaulting and the draft origin of items largely restate the schema's own descriptions, adding little that is not already structured. Baseline 3 is appropriate.

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 ('Save'), resource ('items into one existing collection'), and a concrete scope ('up to 50 items ... in a single step'). It also positions itself against the closest siblings: it consumes the output of draft_collection_items and is the batch counterpart to the single-item add. An agent can distinguish it 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 Guidelines5/5

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

Gives explicit when/when-not: drafts are the default and stay hidden; "status to 'published' only after the user explicitly asks for it," plus a requirement to confirm the public change before calling. It also names the upstream source of inputs (drafts from draft_collection_items that the user kept).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mondovo 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