Skip to main content
Glama
adrmrn

Tidio MCP Server

by adrmrn

Update Contact

update_contact

Update a Tidio contact's details like email, phone, name, consent, or custom properties. Pass only fields to change; omitted fields stay the same.

Instructions

Update a specific contact in Tidio. Pass only the fields you want to update. Omitted fields remain unchanged; null clears the field (except distinct_id, which cannot be cleared).

Args: contact_id (str): Required. The UUID of the contact to update. email (str, optional): Contact email address in RFC822 format. phone (str, optional): Contact phone number. first_name (str, optional): Contact's first name. last_name (str, optional): Contact's last name. email_consent (str, optional): Email consent status. Must be one of: 'subscribed', 'unsubscribed'. distinct_id (str, optional): External system identifier. Maximum 55 characters. Cannot be cleared (null is not accepted). properties (list, optional): List of custom contact properties to update. Each item must be a dict with 'name' (max 128 chars) and 'value' (max 1000 chars) fields. Example: [{"name": "plan", "value": "premium"}, {"name": "score", "value": 42}]

Returns: Dict: A dictionary with success status.

Raises: ValueError: If any of the provided arguments have invalid values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
phoneNo
last_nameNo
contact_idYes
first_nameNo
propertiesNo
distinct_idNo
email_consentNo
Behavior5/5

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

With no annotations, the description fully carries the behavioral burden. It reveals that omitted fields remain unchanged, null clears fields, distinct_id cannot be cleared, and it raises ValueError on invalid arguments. It also states the return type.

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?

The description uses a clear Args/Returns/Raises structure, front-loads the most important semantics, and every sentence adds value. It is detailed but not verbose.

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

Completeness5/5

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

Given the tool's complexity (8 parameters, mixed null semantics, special rules), the description is complete. It covers parameter constraints, return values, error behavior, and examples, and no output schema or annotations exist to fill gaps.

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

Parameters5/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 thoroughly. Every parameter is documented with format, constraints, and examples (e.g., email RFC822, distinct_id max 55 chars, properties structure).

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 description clearly states 'Update a specific contact in Tidio' with a specific verb and resource. It distinguishes itself from sibling tools like create_contact and delete_contact by focusing on updating an existing contact.

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 provides clear usage context: 'Pass only the fields you want to update' and explains omission/null behavior. However, it does not explicitly mention when not to use it or name alternative tools, so it falls 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adrmrn/tidio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server