Skip to main content
Glama
mark-o298

Respond.io MCP Server

by mark-o298

create_contact

Create a contact by providing an identifier (email or phone) and first name, with optional phone, email, language, last name, and custom fields.

Instructions

Create a new contact in the workspace.

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, 'ms' for Malay).
lastNameNoThe last name of the contact.
firstNameYesThe first name of the contact.
identifierYesThe contact's identifier, using their phone or email, formatted as 'email:user@example.com' or 'phone:+1234567890'.
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?

With no annotations present, the description must fully disclose behavioral traits. It identifies the tool as a mutation ('Create') but does not mention any side effects, validation rules, duplication checks, or required permissions. The identifier format is described in the schema but not reiterated in the description.

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 description is very concise, consisting of a single sentence that front-loads the key action and resource. However, the brevity sacrifices important contextual information that could be included without significant length.

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 7 parameters and a rich sibling tool set, the description is insufficient. It does not explain the special 'identifier' format, the optional nature of custom_fields, or constraints on email/phone. The output (response) is also not mentioned.

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 100%, so the baseline is 3. The description adds no parameter semantics beyond what is already in the input schema, which is adequate but not improved upon.

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 clearly states the action ('Create') and the resource ('a new contact') and specifies the scope ('in the workspace'). It effectively distinguishes from sibling tools like 'delete_contact' and 'list_contacts', but does not differentiate from 'create_or_update_contact', which has overlapping functionality.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternative tools such as 'create_or_update_contact' or 'update_contact'. The agent receives no context about prerequisites, failure scenarios, or typical use cases.

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