Spun WhatsApp MCP

Unarchive task

unarchive_task

Idempotent

Bring an archived task in a shared project back to the active lists. Unarchiving an active task reports changed=false.

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": {
      "task_id": "<task_id>"
    },
    "name": "unarchive_task"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes

Output Schema

Name	Required	Description	Default
`changed`	Yes
`task_id`	Yes
`archived`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, so the safety bar is lower. The description adds real value by disclosing the no-op contract ('Unarchiving an active task reports changed=false') and the shared-project scope constraint. It stops short of stating permission requirements or what errors occur on invalid task IDs.

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?

Two short sentences with no filler; the primary action is front-loaded and the edge-case behavior follows. Every sentence earns its place.

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?

For a one-param mutation with an output schema (which presumably carries the 'changed' field) and full annotation coverage, this is nearly complete: scope, action, and no-op behavior are all covered. Only permission/error behavior for non-archived or cross-project tasks is missing.

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?

Single required param with 0% schema description coverage, so the description carries the burden — but it says nothing about task_id (e.g. that it is a numeric string ID, or that it must reference a task in an archived shared project). The param is obvious from the name, so this is a minor but real gap.

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 ('bring back to active lists') and resource ('archived task in a shared project'), which is immediately distinguishable from the sibling archive_task. An agent can tell what this does without opening the schema.

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 implied by the word 'archived' — call it on an archived task — but the description never states prerequisites, exclusions, or names the inverse sibling archive_task as context. The second sentence covers only one edge case rather than giving real when-to-use guidance.

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

All Spun WhatsApp MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?