Skip to main content
Glama
zernio-mcp
by Eyalm321

zernio_update_conversation_status

Archive a conversation or set it back to active.

Instructions

Archive a conversation or set it back to active.

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": {
      "conversationId": "<conversationId>",
      "status": "<status>",
      "accountId": "<accountId>"
    },
    "name": "zernio_update_conversation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesNew status: archived, or active to unarchive
accountIdYesThe Zernio account ID the conversation belongs to (accountId from zernio_list_conversations); the API requires it
conversationIdYesThe conversation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.0
    • addedInput schema / properties / accountId
      Added value: +{
      +  "description": "The Zernio account ID the conversation belongs to (accountId from zernio_list_conversations); the API requires it",
      +  "type": "string"
      +}
    • changedInput schema / properties / status / description
      Previous value: -"New status for the conversation"New value: +"New status: archived, or active to unarchive"
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "read",
      -  "unread",
      -  "archived",
      -  "unarchived"
      -]New value: +[
      +  "active",
      +  "archived"
      +]
    • changedInput schema / required
      Previous value: -[
      -  "conversationId",
      -  "status"
      -]New value: +[
      +  "conversationId",
      +  "status",
      +  "accountId"
      +]
  2. First observedv2.1.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose the key behavioral trait that the operation is a reversible two-state toggle (archived vs. back to active), which is valuable. It omits permissions/auth requirements, whether archiving has side effects on messages or automations, and idempotency behavior.

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?

A single front-loaded sentence with zero filler; the primary action and its inverse are both stated in one clause.

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 simple three-parameter mutation with fully documented schema and no output schema, the description covers the operation and its reversibility. The main residual gap is side effects/permissions, but the schema does heavy lifting here.

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 the schema already documents all three parameters, including the enum and the note that accountId comes from zernio_list_conversations. The description adds no parameter meaning 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair and resource: 'Archive a conversation or set it back to active.' An agent can immediately tell this toggles a conversation's archived/active state. It does not, however, differentiate itself from siblings like zernio_update_campaign_status, which share the same status-toggle shape.

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?

No guidance on when to prefer this over alternatives (e.g., zernio_create_conversation or zernio_get_conversation), no prerequisites, and no note that accountId must be sourced from zernio_list_conversations before calling. The only usage hint lives in the parameter 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.

Deploy Server

Other Tools