Skip to main content
Glama

Publish course

publish_course
DestructiveIdempotent

Publishes the current course draft only after explicit user confirmation. The operation is rejected when readiness has blocking errors. Returns editor and short-lived learner preview links.

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": {
      "course_id": "<course_id>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>",
      "confirmation": "<confirmation>"
    },
    "name": "publish_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
confirmationYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare destructive, non-read-only, idempotent, and closed-world behavior. The description adds useful context beyond them: explicit user confirmation, readiness-based rejection, and returned editor and short-lived learner preview links.

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 compact sentences, front-loaded with the action and the key confirmation precondition. Every sentence adds useful information with no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, confirmation, readiness rejection, and return links, which is meaningful for a destructive publish action. However, for a tool with four required parameters and no output schema, it leaves the revision and idempotency semantics unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all four parameters are required, so the description must carry parameter meaning. It only indirectly implies the confirmation parameter and says nothing about course_id, expected_revision, or idempotency_key, which are critical for correct invocation.

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: publishing the current course draft. It is clear enough to distinguish this from unrelated course-management siblings, though it does not explicitly contrast with publish_library_content or unpublish_course.

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 an important prerequisite: use only after explicit user confirmation, and it explains a rejection condition when readiness has blocking errors. It does not name alternative tools or spell out when to unpublish or publish library content instead.

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