Skip to main content
Glama

SalesBlink Cold Email

Archive List

archive_list
Destructive

Archive or Unarchive a List - Archive lists to remove them from active views

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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe list ID
forceNoArchive even if sequences use this list. 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 list. 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
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's obligation is lighter. The description reinforces the effect on active views but says nothing about reversibility (that archiving can be undone with archived=false), nothing about the IN_USE failure path or the risk of forcing, all of which matter for a destructive mutation. It adds some context beyond annotations but leaves the key behavioral risks to the schema.

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?

A single short sentence, front-loaded with the verb pair and resource, with the effect clause earning its place. The phrasing is slightly redundant in restating 'Archive or Unarchive a List' before explaining the effect.

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 output schema and fully described input schema mean the description need not explain returns, and annotations cover the safety profile. However, for a destructive toggling operation the description omits the reversible nature of archiving and the conditional failure/confirmation behavior, leaving it only minimally adequate.

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 every parameter including force, archived, and workspace_id is already documented with meaning and consequences. The description adds no parameter-level detail, which is acceptable at full coverage but earns only the baseline.

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 a specific resource (List), and adds the effect ('remove them from active views'), which distinguishes it from siblings like archive_sequence or archive_contact by resource alone. It stops short of explicitly differentiating itself from those siblings, so it is clear but not fully self-locating.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over alternatives, nor any mention of the 'archived' flag flipping the operation to unarchive beyond the title. The only hint of usage is the result ('remove them from active views'), which is an outcome, not a selection rule or prerequisite.

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.