Skip to main content
Glama

Messaging: Set composing

messaging_set_composing
Destructive

Publish a typing or voice-recording composing signal in a known chat where supported (LinkedIn Classic, WhatsApp and Facebook). This is ephemeral provider state; use only when an agent workflow explicitly needs it.

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": {
      "chat_id": "<chat_id>",
      "action": "<action>"
    },
    "name": "messaging_set_composing"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
chat_idYesExact chat/conversation ID from the appropriate chat/inbox listing or resolver. Never pass a person name or user ID. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds real value beyond them by disclosing that the resulting state is ephemeral provider state and that support is provider-dependent, which explains why calling it is usually pointless to repeat and may not work everywhere. It does not address failure behavior on unsupported providers or whether an error is returned.

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 sentences, front-loaded with the action and scope, followed by the constraint and the caution. Nothing is redundant or padded.

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 tool with no output schema, the description covers purpose, provider support, ephemerality, and a usage caution. Remaining gaps are modest: no statement of behavior on unsupported providers and no confirmation that a successful call returns no durable result.

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 67%: chat_id and account_id are well documented in-schema, but the action enum has no description. The description compensates by spelling out the two signal kinds ('typing or voice-recording composing signal'), mapping those to the enum values and clarifying what the parameter means semantically.

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 and resource ('Publish a typing or voice-recording composing signal') plus the scope ('in a known chat') and the providers where it works. This clearly separates it from messaging_send_message, messaging_set_presence, and messaging_set_chat_state.

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

Usage Guidelines4/5

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

Gives explicit usage guidance: 'use only when an agent workflow explicitly needs it,' which tells the agent this is a narrow, opt-in capability, and the provider list scopes applicability. It does not name sibling alternatives (e.g., set_presence for online status) or say what to do on unsupported providers, so it stops short of full when/when-not routing.

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.