Skip to main content
Glama
ignytehq

plunk-mcp

Official
by ignytehq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update contact

plunk_update_contact
Idempotent

Update a contact's email address or custom fields, modifying only the fields you supply. Use to correct an address or set custom data; not for subscription changes.

Instructions

Purpose: Change a contact's email address or custom data. Only the fields supplied are modified.

Not for: Changing subscription state, which has its own tools: plunk_subscribe_contact and plunk_unsubscribe_contact.

Returns: The updated contact.

Use when: Correcting an address or setting custom fields.

Note: In the data object, null deletes a key, empty strings are ignored, and reserved keys are filtered. Changing an email to one already in use returns 409.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
dataNo
emailNo
subscribedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / data / propertyNames
      Added value: +{
+  "type": "string"
+}
  2. First observedv1.2.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare the safety profile (idempotent, non-destructive, open-world). The description goes well beyond that: null deletes a key in data, empty strings are ignored, reserved keys are filtered, and a duplicate email produces a 409. These are exactly the behaviors an agent needs and that annotations cannot express.

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?

Bold-labelled sections (Purpose / Not for / Returns / Use when / Note) make it skimmable and front-loaded. Every sentence conveys a distinct, actionable fact with no padding.

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

Completeness5/5

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

For a patch-style mutation with no output schema, the description covers what changes, what is preserved, returns ('The updated contact'), the error case (409), and the key scoping rules. It is complete enough to invoke correctly.

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 0%, so the description must carry the load, and it does for the tricky `data` object (null-delete, empty-string, reserved-key rules). However it never explains `id` (required) and is silent on the `subscribed` boolean that exists in the schema, which sits awkwardly beside the 'Not for subscription state' guidance and could confuse an agent about whether that param is usable.

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?

States a specific verb and resource ('Change a contact's email address or custom data'), and immediately scopes it ('Only the fields supplied are modified'). It also names the sibling tools it is not the same as (plunk_subscribe_contact / plunk_unsubscribe_contact), so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

Explicit 'Use when' clause ('Correcting an address or setting custom fields') plus a 'Not for' exclusion naming the two alternative tools for subscription changes. Both the positive and negative selection conditions are given; nothing is left to inference.

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