Skip to main content
Glama
smallest-inc

Smallest MCP Server

Official
by smallest-inc

publish_draft

Publish a draft as a new version and activate it live after a security check; discard if needed.

Instructions

Publish a draft as a new version and (by default) activate it to make it live. Publishing triggers an async security check on the prompt; this tool waits for it to pass before activating and reports the real outcome — if the check is still pending after ~60s the version is published but NOT live yet (use activate_version once it passes), and if it fails the version cannot be activated until the prompt is fixed. Can also discard a draft instead of publishing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoVersion label (max 200 chars, e.g. 'Changed voice to yuvika')
actionNoWhether to publish the draft (make it live) or discard itpublish
activateNoActivate the published version once its security check passes (default true). Pass false to publish only — activate later with activate_version.
agent_idYesThe agent ID
draft_idYesThe draft ID to publish (returned by update_agent_config, update_agent_prompt, add_agent_tool, set_pre_call_api, etc.)
descriptionNoChangelog description (max 2000 chars)
Behavior5/5

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

No annotations exist, so the description fully discloses the async security check, ~60s timeout, conditions for not activating, and the ability to discard. This is comprehensive and beyond typical expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph that front-loads the main purpose, but it is information-dense and could benefit from bullet points for clarity. Still, it is concise relative to the complexity.

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

Completeness5/5

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

For a tool with 6 parameters, no output schema, and no annotations, the description is remarkably complete. It explains async behavior, security check outcomes, activation, and discarding, leaving no major gaps.

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 coverage is 100%, so baseline is 3. The description adds limited value beyond schema, only providing context for action (publish/discard) and activation default. No new parameter meaning is added.

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?

The description clearly states the tool publishes a draft as a new version and activates it by default, with an option to discard. It distinguishes from sibling tool 'activate_version' by mentioning its own async behavior and alternative.

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?

The description explains when to use the tool (to publish a draft) and provides guidance on the async security check, outcomes, and alternative use of activate_version. It could explicitly state when not to use, but the context is clear.

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/smallest-inc/mcp-server'

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