Tidio MCP Server and API by Cotlet

Create macro in Tidio

tidio_create_macro

Read-onlyIdempotent

Create macro in the user's own Tidio account from ChatGPT, Claude or any AI agent. Returns how to do it in Tidio step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Tidio Cloud Browser. Tidio's official API: Tidio has a REST API, the OpenAPI, for contacts, tickets, operators and departments, but only on the Plus and Premium plans, and its two official MCP servers cannot work your inbox (checked 17 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": "tidio_create_macro"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/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 is consistent with that by stating it 'opens nothing by itself' and only returns instructions. It adds useful context beyond the annotations: the return is a screen/button/field walkthrough, and the official API is plan-gated (Plus/Premium). The oddly specific 'checked 17 Oct 2026' claim is unverifiable filler.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operative information is front-loaded, but the final sentence about Tidio's official REST API and MCP servers is a tangent that does not help an agent decide or invoke. Length is tolerable but not every sentence earns its 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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does so at a high level (step-by-step screens, buttons, fields). It omits finer detail such as whether the walkthrough is Tidio-version specific, but nothing essential to invoking it is missing.

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?

The tool takes zero parameters, so there is nothing to disambiguate; baseline for a parameterless schema is 4. The description correctly implies no inputs are required to obtain the walkthrough.

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 concrete verb+resource (create a macro in the user's Tidio account) and clarifies the real deliverable: step-by-step instructions rather than an actual write. It also names the follow-on tool family (cotlet_browser_*), which separates it from the tidio_* read/reply siblings. The trailing paragraph about Tidio's REST API adds noise rather than sharpening the purpose.

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 usage context: call this to get the procedure, then execute it with cotlet_browser_* tools in the Cloud Browser, and it explicitly says nothing is opened by the call itself. It does not contrast with cotlet_app_guide or say when a macro is the wrong approach, so no exclusions are offered.

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

All Tidio 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?