Skip to main content
Glama

loops

by io.usefulapi

Update a contact

loops_update_contact
Destructive

Updates (or creates) a contact by email/userId. Upserts — creates the contact if not found. Loops API: PUT /v1/contacts/update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesContact email address (required; identifies the contact).
sourceNoSource label.
userIdNoYour app's user id (alternative identifier).
lastNameNoLast name.
firstNameNoFirst name.
userGroupNoUser group segment name.
propertiesNoArbitrary custom contact properties (string/number/boolean); merged into the request body.
subscribedNoWhether the contact is subscribed to email.
mailingListsNoMap of mailing-list id -> subscribed boolean.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already mark destructiveHint=true; description adds upsert behavior info but lacks details on permissions, rate limits, or effects on existing properties.

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?

Concise two sentences with front-loaded purpose; the API endpoint line is marginally redundant but not wasteful.

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

Completeness3/5

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

With 9 parameters, 100% schema coverage, no output schema, and destructive annotation, the description clarifies upsert but does not explain custom property merging, mailing list handling, or return values.

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 provides 100% description coverage for all 9 parameters; description does not add additional meaning beyond 'Updates (or creates) a contact by email/userId.' Baseline 3.

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 it updates or creates a contact (upsert) and specifies the identifier (email/userId). It distinguishes from sibling loops_create_contact by explicitly mentioning upsert behavior.

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?

Implies usage for updating or creating contacts, but does not explicitly state when to use this tool versus loops_create_contact or any conditions to avoid.

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

All loops 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.7/5.0
Disambiguation5/5

Each tool has a distinct purpose and target resource (contacts, properties, lists, events, transactional emails, API key). No overlap or ambiguity in descriptions.

Naming Consistency5/5

All tools follow a consistent 'loops_verb_noun' pattern in snake_case. Verbs are descriptive and nouns match the resource.

Tool Count5/5

10 tools is well-scoped for the domain, covering contacts, properties, lists, events, transactional emails, and an API test. Neither sparse nor overloaded.

Completeness4/5

Covers core contact CRUD, property creation, listing, and sending capabilities. Minor gap: no update/delete for contact properties, but the surface handles primary workflows.

Resources