Mondovo

Add an item to a collection

add_collection_item

Add ONE item to an existing collection: write a blog post, add a dish, a product, a listing. It is saved as a DRAFT by default and stays hidden from visitors. Set status "published" only when the user explicitly asked for it to go live; a published item is sent to the public site by collection auto-publish, so confirm that public change before calling. Send seo with the item's own page title, meta description, keywords and JSON-LD structured_data — for a blog post especially, since update_page_seo cannot reach item pages. Does not create the collection — use create_collection for that. For several items at once use add_collection_items.

Input Schema

Name	Required	Description
`seo`	No	The item page's SEO: `title` (its <title>; omitted, the page shows "<item title> \| <site name>"), `description` (meta description; omitted, taken from the item's own summary), `keywords`, `og_image_url`, `canonical_url`, `no_index`, `no_follow`, and `structured_data` — the page's JSON-LD as { "schemas": [ { "@type": "BlogPosting", … }, { "@type": "BreadcrumbList", … } ] }, which replaces the schema Mondovo would generate for it.
`slug`	No	URL slug. Omit to derive it from the title.
`title`	Yes	The item's title — a post headline, a product or dish name.
`fields`	No	The item's fields, keyed by the collection's field names (list_collections shows them). An unknown name is refused with the valid list.
`status`	No	Omit to save a DRAFT (hidden from visitors). Set "published" only when the user explicitly asked for it to go live.
`site_id`	Yes	The site the collection belongs to
`user_goal`	No	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.
`collection_type`	Yes	The collection's slug, as list_collections returns it (e.g. "blog", "menu", "products", "faqs").

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

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

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / seo

Added value: +{
+  "additionalProperties": false,
+  "description": "The item page's SEO: `title` (its <title>; omitted, the page shows \"<item title> | <site name>\"), `description` (meta description; omitted, taken from the item's own summary), `keywords`, `og_image_url`, `canonical_url`, `no_index`, `no_follow`, and `structured_data` — the page's JSON-LD as { \"schemas\": [ { \"@type\": \"BlogPosting\", … }, { \"@type\": \"BreadcrumbList\", … } ] }, which replaces the schema Mondovo would generate for it.",
+  "properties": {
+    "canonical_url": {
+      "anyOf": [
+        {
+          "format": "uri",
+          "maxLength": 2000,
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Canonical URL, when this page duplicates another."
+    },
+    "description": {
+      "anyOf": [
+        {
+          "maxLength": 500,
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "This page's meta description. Aim for 150-160 characters."
+    },
+    "keywords": {
+      "anyOf": [
+        {
+          "items": {
+            "maxLength": 100,
+            "type": "string"
+          },
+          "maxItems": 30,
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Target keywords for this page, most important first."
+    },
+    "no_follow": {
+      "description": "true asks search engines not to follow links on this page.",
+      "type": "boolean"
+    },
+    "no_index": {
+      "description": "true asks search engines not to index this page.",
+      "type": "boolean"
+    },
+    "og_image_url": {
+      "anyOf": [
+        {
+          "format": "uri",
+          "maxLength": 2000,
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Social sharing image for this page, overriding the site default."
+    },
+    "structured_data": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "description": "This page's JSON-LD as { \"schemas\": [ { \"@type\": \"BlogPosting\", … }, { \"@type\": \"BreadcrumbList\", … } ] }. Replaces the schema Mondovo would otherwise generate for the page, so include every schema it should carry. \"@context\" is added when absent. Max 50 KB. null clears it (back to the generated schema).",
+          "properties": {
+            "schemas": {
+              "items": {
+                "additionalProperties": true,
+                "properties": {
+                  "@type": {
+                    "anyOf": [
+                      {
+                        "minLength": 1,
+                        "type": "string"
+                      },
+                      {
+                        "items": {
+                          "minLength": 1,
+                          "type": "string"
+                        },
+                        "minItems": 1,
+                        "type": "array"
+                      }
+                    ]
+                  }
+                },
+                "required": [
+                  "@type"
+                ],
+                "type": "object"
+              },
+              "maxItems": 20,
+              "minItems": 1,
+              "type": "array"
+            }
+          },
+          "required": [
+            "schemas"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "This page's JSON-LD as { \"schemas\": [ { \"@type\": \"BlogPosting\", … }, { \"@type\": \"BreadcrumbList\", … } ] }. Replaces the schema Mondovo would otherwise generate for the page, so include every schema it should carry. \"@context\" is added when absent. Max 50 KB. null clears it (back to the generated schema)."
+    },
+    "title": {
+      "anyOf": [
+        {
+          "maxLength": 200,
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "This page's browser-tab title and search headline. Aim for 50-60 characters."
+    }
+  },
+  "type": "object"
+}

First observedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare the generic profile (not read-only, non-idempotent, non-destructive, open-world). The description adds the behavior that matters: items save as DRAFT and stay hidden by default, and a published item is pushed to the public site via collection auto-publish, so the public change should be confirmed first. Those are non-obvious side effects that go well beyond the annotation set.

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?

Front-loads the core action and the draft default, then layers warnings and alternatives. Every sentence carries actionable weight (defaults, publish consequence, SEO rationale, two sibling redirects) with no restatement of the tool name or filler.

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 an 8-parameter mutation tool with nested `seo` and full schema coverage, the description covers defaults, publish side effects, and sibling routing. It says nothing about what a successful call returns (e.g. the new item identifier) or how to follow up with update_collection_item, which would close the loop on a create-then-edit workflow.

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 100%, so the baseline is 3; the description rises above it by explaining why `seo` matters here at all — it carries the item page's own title/meta/keywords/JSON-LD, and notably update_page_seo cannot reach item pages. That cross-tool constraint is unavailable in the schema. It does not add anything about `fields` keying or `slug` derivation, which the schema already covers.

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 resource ('Add ONE item to an existing collection') and immediately grounds it with concrete examples (blog post, dish, product, listing). It explicitly distinguishes itself from both create_collection and add_collection_items, so an agent can pick it without opening a sibling 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?

Explicit routing is given for both alternatives: 'Does not create the collection — use create_collection for that' and 'For several items at once use add_collection_items.' It also states the condition for the risky path ('Set status "published" only when the user explicitly asked for it'), which is exactly the kind of when-to-use guidance the schema cannot express.

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

All Mondovo tools Inspect

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

Need Help?