Skip to main content
Glama
agentisend

agentisend

Publish the draft as a version

publish_template

Publish a template's draft so send_email uses it as the current version. Publishing creates a new immutable version, leaving already sent emails unchanged.

Instructions

Purpose: make a template's draft the version send_email uses. NOT for: editing. Published versions are immutable; publishing again makes the next one, so nothing already sent can change under you. Returns: the template id and the new version number.

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": {
      "template_id": "<template_id>"
    },
    "name": "publish_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYesThe template id from list_templates.
idempotency_keyNoYour own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
template_idNoIdentifier.
version_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With annotations declaring readOnlyHint=false and destructiveHint=false, the description usefully adds that published versions are immutable and that re-publishing creates a new version rather than mutating the old one, plus that already-sent mail is unaffected. It stops short of stating permission/auth requirements or whether the template must already exist, so it is strong but not exhaustive.

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 labeled lines (Purpose / NOT for / Returns) with the core action front-loaded and zero filler. Every clause carries information an agent needs.

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?

An output schema exists, so the brief Returns line is supplementary rather than required. The description covers the key risk (immutability, re-publish semantics) but omits prerequisites such as whether a draft must exist or what happens on an empty draft.

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%: template_id is documented as coming from list_templates and idempotency_key is fully explained with retry semantics. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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 gives a specific verb (publish) plus the precise outcome: making a template's draft the version that send_email uses. This is meaningfully distinct from siblings like list_templates, render_template, and send_email, so an agent can route correctly without opening any schema.

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 'NOT for: editing' line is an explicit exclusion, and the immutability note explains the consequence of repeat invocation ('publishing again makes the next one'). It never names an alternative tool (e.g., render_template for previewing or list_templates for discovery), so it falls short of the full when/when-not/alternatives bar.

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