Skip to main content
Glama

Publish Library item

publish_library_content
DestructiveIdempotent

Publishes one Library draft video, document, or article. Use only after the user explicitly asks to publish it. Articles also require expected_revision from the latest article write or inspection.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content_type": "<content_type>",
      "content_id": "<content_id>",
      "confirmation": "<confirmation>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "publish_library_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_idYes
confirmationYes
content_typeYes
idempotency_keyYes
expected_revisionNoRequired for articles. Use the revision from the latest article write or inspection.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety is partly covered structurally. The description adds real context beyond that: it operates on draft items only, one item per call, and requires an explicit user request plus an expected_revision for articles. It still doesn't say what a successful publish returns or how already-published content is handled.

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, each earning its place: what it does, when it may be used, and a conditional parameter rule. The precondition and the article-specific caveat are front-loaded without padding.

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 destructive, five-parameter mutation with no output schema, the definition covers the essential decision points: scope, user consent, and the article revision requirement, while annotations carry the safety and idempotency profile. It would be stronger with a note on post-publish state or on re-publishing already-published content.

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 only 20%, and the description compensates for the most important case by explaining expected_revision is required for articles and where to obtain it. However, it says nothing about the confirmation const ('PUBLISH') or the idempotency_key, leaving two required parameters to the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Publishes one Library draft video, document, or article') and scopes it to a single item, which separates it from bulk/course siblings like publish_course or import_library_content. It does not explicitly name an alternative tool, so it stops short of full sibling differentiation.

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?

It gives a clear activation precondition: 'Use only after the user explicitly asks to publish it,' which is exactly the gate an agent needs for an irreversible action. It does not name alternatives (e.g., update_library_content or inspect_library_content as prerequisites before publishing), which is the remaining gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources