Skip to main content
Glama

SalesBlink Cold Email

Archive Template

archive_template
Destructive

Archive or Unarchive a Template - Archive email templates

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": {
      "id": "<id>"
    },
    "name": "archive_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe template ID
forceNoArchive even if sequences use this template. Without it such a request fails with code IN_USE naming the sequences; confirm with the user before forcing
archivedNotrue to archive, false to unarchive
workspace_idNoWorkspace ID this action applies to. When omitted, the current or default workspace is used.

Output Schema

NameRequiredDescriptionDefault
resultNoThe raw result returned by the SalesBlink tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / force
      Added value: +{
      +  "description": "Archive even if sequences use this template. Without it such a request fails with code IN_USE naming the sequences; confirm with the user before forcing",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is covered structurally. The description adds only the bidirectional toggle fact (archiving or unarchiving), but omits the significant behavioral trait that archiving a template in use fails with IN_USE unless force is set, and says nothing about permissions or what an unarchive restores.

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?

One short, front-loaded sentence with no wasted preamble. The trailing 'Archive email templates' clause is slightly redundant with the first half but usefully narrows the resource to email templates.

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?

An output schema exists and the input schema is fully specified, so return values and parameters need no prose. What is missing is behavioral context proportionate to a destructive mutation: the forced-archive failure mode and reversibility are not surfaced in the description an agent reads first.

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 all four parameters including the nuanced force/IN_USE interaction and the archived default are already well documented in the schema. The description adds no parameter meaning beyond that, which meets the baseline for fully covered schemas.

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 names a specific verb pair (archive/unarchive) and resource (email templates), which is clear enough to separate it from update_template or delete-type siblings. It does not explicitly name those siblings, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the tool name and the 'Archive or Unarchive' phrasing; there is no statement of when to prefer this over update_template or delete, and no prerequisites mentioned. The important 'when archiving would fail because sequences use it' guidance lives only in the schema, not the description.

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.