Skip to main content
Glama

Publish Multiple

publish_multiple
DestructiveIdempotent

Publish multiple content items simultaneously in LightCMS to streamline content deployment. Use specific IDs or publish all drafts at once instead of individual calls.

Instructions

Publish multiple content items in a single call. Use this instead of calling publish_content in a loop.

Examples:

  • Publish specific pages: {"ids": ["abc123", "def456"]}

  • Publish all drafts at once: {"publish_all_drafts": true}

Returns a list of published IDs and any failures.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoList of content IDs to publish. Mutually exclusive with publish_all_drafts.
publish_all_draftsNoIf true, publish every unpublished (draft) content item in the site
Behavior4/5

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

Annotations cover idempotent/destructive hints, so description adds valuable behavioral context by specifying return format ('list of published IDs') and crucially notes 'any failures' indicating partial success behavior. Could further clarify publish semantics (e.g., making content live/public).

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?

Efficiently structured with purpose statement, usage guideline, bulleted examples, and return description. Zero redundant sentences; every clause adds selection or invocation guidance.

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?

Absence of output schema is compensated by describing return values and failure cases. 100% input schema coverage means parameters are well-documented. Minor gap: does not elaborate on side effects of 'publish' operation (visibility changes, permissions required).

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?

With 100% schema coverage, baseline is 3. Description earns additional point by providing concrete JSON examples showing ID format ['abc123', 'def456'] and boolean usage, adding semantic context beyond the schema's type definitions.

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 specific verb 'Publish' with resource 'content items' and scope 'in a single call'. Explicitly distinguishes from sibling tool 'publish_content' by contrasting batch vs. loop usage.

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?

Contains explicit directive 'Use this instead of calling publish_content in a loop' identifying when to select this tool over its sibling. Examples further clarify both specific ID batching and bulk draft publishing patterns.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jonradoff/lightcms'

If you have feedback or need assistance with the MCP directory API, please join our Discord server