Skip to main content
Glama

simpletexting

by io.usefulapi

Update contact

simpletexting_update_contact
Destructive

UPDATES a live contact — its profile fields, list memberships, and custom fields. This MODIFIES live data. Provide only the fields you want to change. SimpleTexting REST: PUT /contacts/{contactIdOrNumber}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoContact email address.
commentNoFree-text note on the contact.
contactYesContact id or phone number to update.
listIdsNoList ids or names to assign the contact to.
birthdayNoContact birthday (YYYY-MM-DD).
lastNameNoContact last name.
firstNameNoContact first name.
contactPhoneNoNew phone number for the contact.
customFieldsNoCustom field values, as a map of field name → value.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations include destructiveHint=true, and the description reinforces this with 'MODIFIES live data'. It adds context on what is modified (profile fields, list memberships, custom fields) beyond the annotation, though it omits details like irreversibility or side effects.

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?

Three concise sentences: purpose, warning, usage hint + API reference. No fluff, front-loaded with the action.

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?

Given the complexity (9 params, 1 required) and absence of output schema, the description explains the resource and mutation behavior adequately. It could clarify that unprovided fields remain unchanged, but the partial-update hint covers that implicitly.

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?

Schema coverage is 100% with descriptions for all 9 parameters. The description adds the critical insight that only changed fields need be provided, aiding correct usage. This goes beyond basic schema info.

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?

Description clearly states the verb (UPDATES), resource (live contact), and scope (profile fields, list memberships, custom fields). It also references the underlying REST endpoint, distinguishing it from sibling tools like list or get contacts.

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 hint 'Provide only the fields you want to change' guides partial-update usage, but the description does not explicitly state when to use this tool versus alternatives (e.g., create or delete) or list prerequisites.

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

All simpletexting toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: evaluate vs send, get vs list for campaigns/contacts/media/messages, and update for contacts. No overlapping purposes.

Naming Consistency5/5

All tools follow a consistent 'simpletexting_verb_noun' pattern with lowercase and underscores. Verbs are imperative (evaluate, get, list, send, update) and nouns use singular for get and plural for list, as expected.

Tool Count5/5

11 tools is well-scoped for a messaging API, covering the core operations without being excessive. Each tool serves a clear purpose and earns its place.

Completeness2/5

Significant gaps exist: no create or delete for contacts, campaigns, or media; no delete for messages. The surface is read-heavy with only send and update as write operations, limiting full lifecycle management.

Resources