JivoChat MCP Server and API by Cotlet

Merge clients in JivoChat

jivochat_merge_clients

Read-onlyIdempotent

Merge clients in the user's own JivoChat account from ChatGPT, Claude or any AI agent. Returns how to do it in JivoChat step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's JivoChat Cloud Browser. JivoChat's official API: JivoChat has four developer APIs, Widget, Webhooks, Chat and Bot, but no REST API to read chats, clients or history, and no official MCP server (checked 20 Oct 2026).

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": "jivochat_merge_clients"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself,' which resolves the apparent conflict between a 'merge' name and a read-only hint. It also discloses that the return value is a step-by-step procedure (screens, buttons, fields) and documents the API limitation that forces browser automation. It stops short of saying whether an open browser tab or prior navigation is required.

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 first sentence about ChatGPT, Claude or any AI agent is marketing padding, and the API-catalog sentence is long, but the key operational facts (returns instructions, opens nothing, use cotlet_browser_*) are front-loaded and earn their place.

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 no-parameter, no-output-schema guide tool, the description covers what is returned, why browser automation is required, and how to continue, which is enough for an agent to call it correctly. Minor gaps remain around preconditions such as whether a Cloud Browser session must already exist.

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?

With zero parameters, there is nothing for the description to disambiguate, and the schema is trivially complete. Baseline 4 applies.

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 states a specific verb and resource (merge clients in JivoChat) and immediately clarifies the non-obvious twist: the tool returns step-by-step instructions rather than performing the merge. This distinguishes it from a real mutation API call, though the name alone would mislead, since no sibling is named as the alternative for actually executing the merge.

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 workflow guidance: call this first for the procedure, then perform the action with cotlet_browser_* tools in the user's JivoChat Cloud Browser. It explains the rationale (no REST API exists), but offers no explicit when-not condition or named alternative for the merge itself.

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

All JivoChat MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?