Skip to main content
Glama

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Messaging: Start chat

messaging_start_chat
Destructive

Start a new WhatsApp, Instagram or Telegram one-to-one/group chat by sending its first message. Resolve users_ids first. A string starts 1-to-1; an array requests a group. LinkedIn requires the inbox-specific start tool.

Input Schema

NameRequiredDescriptionDefault
nameNo
textYes
providerYes
specificsNo
users_idsYesOne exact provider user ID for a direct chat, or exact provider user IDs for a group; resolve every recipient first.
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.
attachmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / users_ids / anyOf
      Previous value: -[
-  {
-    "description": "Exact provider user ID returned by the relevant profile/contact resolver; never a display name or profile URL. For LinkedIn, use the stable system ID. LinkedIn system user ID: Stable LinkedIn/Unipile user id, commonly ACo... for Classic profiles. Obtain with: linkedin_get_profile_from_url(profile_url) -> result.id; linkedin_get_profile(user_id_or_public_identifier) -> result.id; linkedin_search_people(...) -> selected result.id Never pass: full linkedin.com/in/... URL, person name, company ID.",
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "items": {
-      "description": "Exact provider user ID returned by the relevant profile/contact resolver; never a display name or profile URL. For LinkedIn, use the stable system ID. LinkedIn system user ID: Stable LinkedIn/Unipile user id, commonly ACo... for Classic profiles. Obtain with: linkedin_get_profile_from_url(profile_url) -> result.id; linkedin_get_profile(user_id_or_public_identifier) -> result.id; linkedin_search_people(...) -> selected result.id Never pass: full linkedin.com/in/... URL, person name, company ID.",
-      "minLength": 1,
-      "type": "string"
-    },
-    "minItems": 1,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "description": "Exact provider user ID returned by the relevant profile/contact resolver; never a display name or profile URL. For LinkedIn, use the stable system ID. LinkedIn system user ID: Stable LinkedIn user id, commonly ACo... for Classic profiles. Obtain with: linkedin_get_profile_from_url(profile_url) -> result.id; linkedin_get_profile(user_id_or_public_identifier) -> result.id; linkedin_search_people(...) -> selected result.id Never pass: full linkedin.com/in/... URL, person name, company ID.",
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "items": {
+      "description": "Exact provider user ID returned by the relevant profile/contact resolver; never a display name or profile URL. For LinkedIn, use the stable system ID. LinkedIn system user ID: Stable LinkedIn user id, commonly ACo... for Classic profiles. Obtain with: linkedin_get_profile_from_url(profile_url) -> result.id; linkedin_get_profile(user_id_or_public_identifier) -> result.id; linkedin_search_people(...) -> selected result.id Never pass: full linkedin.com/in/... URL, person name, company ID.",
+      "minLength": 1,
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  }
+]
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the agent knows this is a non-idempotent write. The description's 'by sending its first message' corroborates that but adds little beyond the annotations — no auth requirements, rate limits, or what happens on failure are disclosed.

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?

Three short sentences, front-loaded with the core action and followed by the two routing constraints an agent most needs. No filler, though the LinkedIn sentence could arguably be tighter.

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

Completeness3/5

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

For a 7-parameter tool with nested attachment objects and no output schema, the description covers the main chat-initiation flow well but leaves optional parameters (attachments, specifics, account_id handling) unaddressed. Adequate but with visible gaps.

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

Parameters2/5

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

Schema description coverage is only 29%, yet the description's parameter detail (string vs array for users_ids) merely restates what the users_ids schema description already says. Attachments, specifics, name, and text remain undocumented in both places, so the description does not compensate for the low coverage.

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?

The first sentence names a specific verb (start), the resource (chat), the providers (WhatsApp, Instagram, Telegram), and the scope (one-to-one/group via first message). It also distinguishes itself from the LinkedIn-specific start tools, so an agent can tell it apart from the many messaging siblings.

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?

It gives clear preconditions ('Resolve users_ids first') and routing rules ('A string starts 1-to-1; an array requests a group', 'LinkedIn requires the inbox-specific start tool'). It doesn't explicitly contrast with messaging_send_message or messaging_send_to_contact, but the context needed to pick this tool is well supplied.

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

All Nilyo toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources