Skip to main content
Glama
metavert-io

LightCMS

by metavert-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Update Content by Path

update_content_by_path
DestructiveIdempotent

Change page content by URL path instead of MongoDB ID—ideal when you know the web address but not its database identifier.

Instructions

Update content identified by its URL path instead of its ID. Useful when you know the page URL but not the MongoDB ID.

Example: {"path": "/about", "title": "About Us", "data": {"body": "Updated content"}}

The path always resolves to the live page, never to a fork copy (inside an agent sandbox the write goes to the sandbox copy as usual).

Only the fields you provide are changed. Always include a version_comment describing what changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoField values to update
holdNotrue puts the page on hold so it cannot be published; false clears the hold. Holding a published page does not unpublish it
pathYesURL path of the content to update (e.g. /about or /blog/my-post),required
tagsNoTags for lc:query index pages
titleNoNew title
noindexNotrue hides the page from search engines and AI; false makes it visible again
categoryNoContent category
og_imageNoOpen Graph image URL
publishedNoPublish state
author_urlNoAuthor profile URL; empty string clears it
author_nameNoAuthor name for structured data and feeds; empty string reverts to the site default
version_commentNoVersion comment
meta_descriptionNoSEO meta description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv7.3.4
    • addedInput schema / properties / author_name
      Added value: +{
+  "description": "Author name for structured data and feeds; empty string reverts to the site default",
+  "type": [
+    "null",
+    "string"
+  ]
+}
    • addedInput schema / properties / author_url
      Added value: +{
+  "description": "Author profile URL; empty string clears it",
+  "type": [
+    "null",
+    "string"
+  ]
+}
    • addedInput schema / properties / hold
      Added value: +{
+  "description": "true puts the page on hold so it cannot be published; false clears the hold. Holding a published page does not unpublish it",
+  "type": [
+    "null",
+    "boolean"
+  ]
+}
    • addedInput schema / properties / noindex
      Added value: +{
+  "description": "true hides the page from search engines and AI; false makes it visible again",
+  "type": [
+    "null",
+    "boolean"
+  ]
+}
  2. First observedv4.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: the path resolves to the live page and never a fork, except inside an agent sandbox where the write hits the sandbox copy, plus PATCH-style 'only fields you provide are changed' semantics. It omits permission/auth requirements and lock interplay.

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?

The distinguishing fact (path vs ID) is front-loaded, followed by a compact example and then the two behavioral caveats. Every sentence carries distinct information; none repeats the schema 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 13-parameter destructive mutation with no output schema, the description covers purpose, partial-update semantics, fork/sandbox resolution, and the version_comment requirement. It leaves out permission/lock requirements and any approval-workflow interaction present among siblings, but is otherwise sufficient to call correctly.

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 goes beyond it by supplying a worked example, stating that unlisted fields are untouched, and telling the agent to always include version_comment – semantic guidance the schema only labels generically.

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+resource (update content) plus the scoping key (by URL path) and explicitly distinguishes itself from the ID-based variant ('instead of its ID'). An agent can tell this apart from sibling update_content without opening either 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?

Gives clear when-to-use guidance: 'Useful when you know the page URL but not the MongoDB ID,' which implicitly routes the agent away from the ID-based tool. It does not name the alternative tool explicitly or mention any exclusions (e.g., when a lock or approval is required instead).

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

Deploy Server

Other Tools