Skip to main content
Glama
ignytehq

plunk-mcp

Official
by ignytehq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Unsubscribe contact

plunk_unsubscribe_contact
Idempotent

Opt a contact out of marketing email while keeping their record, so they are not mailed again. Use when someone asks to stop receiving mail; transactional mail is unaffected.

Instructions

Purpose: Opt a contact out of marketing email. Transactional mail is unaffected.

Not for: Erasing them, which is plunk_delete_contact. Unsubscribing keeps the record that they opted out, which is what prevents them being mailed again.

Returns: The updated subscription state.

Use when: Someone asks to stop receiving mail. This is almost always the right tool rather than deletion.

Note: If they only want a break rather than to leave, plunk_snooze_contact pauses email for a set period and resubscribes them afterwards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContact's PUBLIC id — the id embedded in unsubscribe links, distinct from the regular UUID. Get it from plunk_get_contact (returns it alongside the regular id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish non-read-only, idempotent, non-destructive behavior, and the description adds meaningful context beyond them: the contact record is retained, that retention is what prevents future mailing, and transactional mail is unaffected. It lacks detail on permissions/error behavior, but the safety-relevant semantics are well disclosed.

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-labeled sections (Purpose, Not for, Returns, Use when, Note) front-load the key facts and route to alternatives. Every sentence carries distinct information; nothing is redundant filler.

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?

With no output schema, the description supplies the return value ('updated subscription state'), the effect on the record, and the routing alternatives. Nothing an agent needs to invoke this correctly is missing.

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?

There is only one parameter and schema coverage is 100%, with the schema itself explaining that the id is the PUBLIC id embedded in unsubscribe links. The description adds no parameter-level information, so the schema does all the work – the expected baseline of 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?

States a specific verb+resource (opt a contact out of marketing email) and immediately scopes what is not affected (transactional mail). It also names the sibling it differs from (plunk_delete_contact) and a near-alternative (plunk_snooze_contact), so an agent can distinguish it without opening other 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' guidance ('someone asks to stop receiving mail'), an explicit 'Not for' exclusion routing to plunk_delete_contact, and a conditional alternative to plunk_snooze_contact for temporary breaks. All when/when-not/alternatives are covered.

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