Skip to main content
Glama
mark-o298

Respond.io MCP Server

by mark-o298

create_or_update_contact

Create a new contact or update an existing one using a unique identifier. Matches by ID, email, or phone to keep contact data consistent.

Instructions

Create a contact if they do not exist, or update the existing contact. Uses the contact identifier to match.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoThe contact's email address.
phoneNoThe contact's phone number, including the country code (e.g., +60123456789).
languageNoThe contact's language code, based on the ISO 639-1 standard (e.g., 'en' for English).
lastNameNoThe last name of the contact.
firstNameYesThe first name of the contact.
identifierYesThe contact's identifier. Can be the contact's ID, email, or phone number.
custom_fieldsNoAn array of custom field objects, each with a name and value.
Behavior2/5

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

No annotations provided, so description carries full burden. It states upsert behavior but does not disclose whether fields not provided are preserved or overwritten, nor any idempotency, authentication, or response details.

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 is two sentences with no redundant information. It is appropriately sized and front-loads the core action.

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

Completeness2/5

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

Given no annotations, no output schema, and moderate complexity, the description is incomplete. It does not mention return values, partial update behavior, or any potential side effects, which are critical for an upsert tool.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds no extra meaning beyond schema, merely referencing 'identifier'.

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 the tool creates or updates a contact based on an identifier, distinguishing it from separate create and update tools. The verb 'create_or_update' and resource 'contact' are specific.

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 implies usage for upsert operations but does not explicitly compare to 'create_contact' or 'update_contact' siblings. It lacks guidance on when to choose this tool over alternatives.

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/mark-o298/respondio-mcp-server'

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