Skip to main content
Glama
hostinger

hostinger-api-mcp

Official
by hostinger
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Create new contacts

reach_createNewContactsV1

Create a contact in your email marketing list with email and optional details like name, phone, or tags. If double opt-in is enabled, the contact stays pending until confirmation.

Instructions

Create a new contact in the email marketing system.

This endpoint allows you to create a new contact with basic information like name, email, and surname.

If double opt-in is enabled, the contact will be created with a pending status and a confirmation email will be sent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoname parameter
noteNonote parameter
emailYesemail parameter
phoneNoPhone number in E.164 format (leading "+" then 7-15 digits)
surnameNosurname parameter
tag_uuidsNoExisting tags to attach to the created contact
profileUuidYesProfile uuid parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.45.5
    • addedInput schema / properties / tag_uuids
      Added value: +{
+  "description": "Existing tags to attach to the created contact",
+  "items": {
+    "description": "tag_uuids parameter",
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Addedv1.5.0
  3. Removedv1.2.1
  4. Addedv0.2.2
  5. Removedv0.2.1
  6. Addedv0.1.40

TDQS

B3.3/5.0
Behavior4/5

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

The description adds valuable behavioral context beyond the readOnlyHint=false and destructiveHint=false annotations: if double opt-in is enabled, the contact is created with pending status and a confirmation email is sent. It does not cover duplicate handling or profileUuid requirements, but the disclosed behavior is meaningful for an agent.

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 short and front-loads the core purpose. The second sentence is slightly redundant with the first, but it adds concrete field examples and the double opt-in note is relevant. Overall, it is concise with minimal waste.

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?

With no output schema, the description does not explain what is returned on success or failure. It also does not clarify how this relates to reach_createANewContactV1 or bulk creation, and it omits important operational context such as duplicate emails, required profile semantics, and tag handling. The description is not complete enough for polished agent invocation.

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 mentions name, email, and surname as basic info, but does not clarify the meaning of the required profileUuid, the behavior of optional fields like note or phone, or how tag_uuids interacts with contact creation. The schema descriptions are largely tautological, so no additional semantic value is provided.

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 a new contact in the email marketing system.' This is a specific verb and resource. However, it does not distinguish this tool from the sibling reach_createANewContactV1 or the bulk variant reach_createContactsInBulkV1, both of which appear nearby.

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?

There is no guidance on when to use this tool versus the similar sibling tools. The description only restates what the endpoint does, with no exclusions, prerequisites, or alternatives, so an agent cannot decide between this and related contact-creation tools.

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

Deploy Server

Other Tools