Skip to main content
Glama

Messaging: Set presence

messaging_set_presence
Destructive

Set the connected messaging account presence where the provider supports it (LinkedIn Classic, WhatsApp, Telegram; Facebook: online/offline only). Use only for an explicit presence request.

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": {
      "presence": "<presence>"
    },
    "name": "messaging_set_presence"
  }
}

Input Schema

NameRequiredDescriptionDefault
presenceYes
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

A3.9/5.0
Behavior3/5

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

The annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false), so the mutation profile is known without the text. The description does add behaviour the annotations cannot: a provider support matrix and the Facebook-only online/offline restriction. It leaves out what happens on an unsupported provider (silent no-op vs error) and whether the change is visible to contacts, which are the traits an agent would still need.

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, no filler, and the operation and its provider scope are front-loaded before the usage restriction. Every clause carries information the schema and annotations do not.

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 two-parameter state-setting tool with annotations covering the mutation profile, the description supplies purpose, provider coverage, enum caveats and a usage guardrail. What remains thin is failure behaviour on unsupported providers, which is not covered anywhere else in the definition.

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 only 50%: account_id carries a rich description, but the presence enum lists four values with no per-provider meaning. The description compensates by stating which providers accept which values ('Facebook: online/offline only'), which is exactly the missing semantics an agent needs to avoid an invalid call.

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 gives a specific verb and resource ('Set the connected messaging account presence') and scopes it to providers that support the feature, with an explicit Facebook caveat. It stops short of naming the neighbouring tools (messaging_set_composing, messaging_set_chat_state), so the distinction from those has to be inferred from the resource name alone.

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?

'Use only for an explicit presence request' is a genuine usage guardrail: it tells the agent not to change presence proactively or as a side effect of other work. It does not name an alternative tool or say what to do when the user asks for something adjacent (typing indicator, chat state), which keeps it short of a 5.

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.