Skip to main content
Glama
1msg MCP

1msg MCP

Official
by 1msg

send_product

Sends a single catalog product or a product list to a chat ID or phone number via the 1msg Chat API for targeted product sharing.

Instructions

Send a single catalog product or a product list. Destination is chatId or phone. action is required:

  • single product: { "catalog_id": "...", "product_retailer_id": "..." }

  • product list: { "catalog_id": "...", "sections": [{ "title": "...", "product_items": [{ "product_retailer_id": "..." }] }] }

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

Input Schema

NameRequiredDescriptionDefault
bodyNo
phoneNo
actionYes
chatIdNo
footerNo
headerNo
quotedMsgIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.2.10
    • addedInput schema / properties / action
      Added value: +{
      +  "additionalProperties": {},
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / body
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / chatId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / footer
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / header
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / payload
      Removed value: -{
      -  "additionalProperties": {},
      -  "propertyNames": {
      -    "type": "string"
      -  },
      -  "type": "object"
      -}
    • addedInput schema / properties / phone
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / quotedMsgId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "action"
      +]
  2. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden and largely does not meet it: it never says that this dispatches a live WhatsApp message, what permissions or catalog setup are required, whether the send is reversible, or what happens if the catalog_id is invalid. The only behavioral content is the required shape of 'action', which is structural rather than behavioral.

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?

The content is front-loaded with the purpose, followed by destination and the required parameter, with compact JSON examples instead of prose. Every line serves a purpose; only the missing coverage of the four other parameters keeps it from being fully tight.

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 a nested object, no annotations, no output schema, and 0% schema coverage, the description is adequate but not sufficient: it documents the required branch and the routing choice but omits the optional text fields and any statement about what a successful send returns. An agent could invoke the two catalog shapes correctly but would be guessing on body/header/footer/quotedMsgId.

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 0%, so the description must compensate, and it does so well for the two hardest inputs: the destination pair (chatId vs phone) and the nested 'action' object, whose two valid shapes are spelled out concretely. It says nothing about the remaining four parameters (body, footer, header, quotedMsgId), leaving half the surface undocumented in both the schema and the description.

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 opening sentence names a specific verb and resource ('Send a single catalog product or a product list') and immediately distinguishes the tool's two operating modes. It does not, however, differentiate itself from the many adjacent send_* siblings such as send_carousel or send_list, which an agent could plausibly confuse it with.

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

Usage Guidelines3/5

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

The description names the addressing targets (chatId or phone) and that 'action' is required, which implies how to invoke it, and the two bullet variants sketch the use cases. There is no explicit guidance on when to choose this over send_carousel, send_list, or send_message, and no preconditions or exclusions are stated.

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