Skip to main content
Glama

Publish stack profile draft

publish_stack_profile_draft
Destructive

Publish a stack profile builder draft as a profile version. A new-profile draft creates the profile (version 1, organisation-visible); a draft editing an existing profile adds the next version. Publish validates the draft (at least one addon or manifest, parents resolve, no plaintext secrets) and redacts ANKRA_SECRET_PARAMETER placeholders into required parameters; validation errors are returned with the offending resources so they can be fixed with the draft edit tools. The draft is consumed on success. Nothing deploys.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "publish_stack_profile_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoRelease channel for the version.stable
draft_idNoUUID of the stack profile builder draft. Defaults to the draft from the current page context, or the organisation's only open draft.
changelogNoChangelog entry for the published version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the key side effect ('the draft is consumed on success'), the validation rules applied (at least one addon or manifest, parents resolve, no plaintext secrets), the secret-redaction behavior, and the error shape. It also explicitly bounds the blast radius with 'Nothing deploys', which reconciles the destructiveHint with agent 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?

Four sentences, each carrying distinct information: outcome, two draft cases, validation/redaction, and consumption. Front-loaded with the core action. The parenthetical rule list is dense but justified by the validation behavior it conveys.

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?

With three optional params, no output schema, and no nested objects, the description covers side effects, validation, and error returns well. The one remaining gap is what a successful publish returns (presumably the new profile version identifier), which the agent must infer.

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 100%, so channel, draft_id, and changelog are already documented including draft_id's page-context fallback. The description adds no further meaning about channel values or changelog formatting; baseline 3 applies when the schema carries the parameter burden.

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 and resource ('Publish a stack profile builder draft as a profile version') and then disambiguates the two draft states: new-profile drafts create version 1, editing drafts add the next version. An agent can distinguish this from create_stack_profile_draft, update_stack_profile, and save_stack_profile_version without inspecting schemas.

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?

Makes clear this is the terminal step for a draft and that validation failures should be repaired with 'the draft edit tools' rather than retried here. It stops short of naming the specific sibling edit tools (add_addon_to_stack_profile_draft, update_addon_in_stack_profile_draft, etc.) or stating when to prefer save_stack_profile_version.

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.