Skip to main content
Glama

Stop capturing a chat's new messages

stop_live_capture
Idempotent

Stop capturing the new messages of WhatsApp chats when the user asks. What was captured stays, and a backfill already accepted (an earlier history the user confirmed, or today's earlier messages) keeps running until it ends; a running history measure is not affected (stop_history_preview stops it). start_live_capture resumes the same conversation later. Pass a list of up to 100 chat_ids to stop several. Name the chat with chat_id, contact_phone or chat_name from list_capturable_chats; phone may be omitted when the user has a single number.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stop_live_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNoThe connected number, from list_connected_numbers. Omit it when the user has a single connected number.
chat_idNoThe chat, by the chat_id list_capturable_chats returns, or a list of 1–100 of them. Pass exactly one of chat_id, contact_phone and chat_name.
chat_nameNoThe chat, by its name exactly as list_capturable_chats returns it. Pass exactly one of chat_id, contact_phone and chat_name.
contact_phoneNoThe chat, when it is a 1:1: the other party's number in E.164. Pass exactly one of chat_id, contact_phone and chat_name.

Output Schema

NameRequiredDescriptionDefault
noteNoWhat happened, to tell the user.
resultsNoBatch only: one per distinct chat_id, in input order.
stoppedNoTrue when this call stopped the new messages.
conversation_idNo
conversation_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive mutation, and the description adds real context beyond that: already-captured data is preserved, in-flight backfills continue to completion, and the history measure is untouched. It does not cover whether stopping immediately halts capture or takes effect at some boundary, which keeps it short of a 5.

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?

Front-loaded with the core action and every sentence carries information, but the second half is a long semicolon-chained block that mixes state guarantees, sibling routing, and parameter rules, which slows parsing slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the description covers action, state effects, alternatives, and batch/identification rules. Nothing an agent needs to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 is the floor. The description still adds value by giving the 1–100 batch limit for chat_id lists, pinning the identity values to list_capturable_chats, and explaining when phone may be omitted.

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 precise verb+resource+scope: 'Stop capturing the new messages of WhatsApp chats'. It is immediately separable from start_live_capture (resume) and stop_history_preview (history measure), naming both explicitly.

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

Usage Guidelines5/5

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

Gives the triggering condition ('when the user asks'), the legitimate alternative (start_live_capture resumes later), and an explicit boundary: stopping does not stop an accepted backfill or a running history measure — for that, use stop_history_preview.

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.

Resources