Skip to main content
Glama
shipmail-to

shipmail-mcp

by shipmail-to
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

Update Webhook

shipmail_update_webhook
DestructiveIdempotent

Modify webhook configuration including URL, events, description, or active status. URL changes redirect all future deliveries.

Instructions

Update webhook URL, subscribed events, description, or active state. Changing the URL silently redirects all future deliveries; treat as destructive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesShipMail resource ID.
urlNo
activeNo
eventsNo
descriptionNo
idempotency_keyNoOptional idempotency key. If omitted, the MCP server generates one for POST tools.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
webhookYes

Schema Changelog

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

  1. Changed5 schema fields changedv0.1.10
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "message.received",
-  "message.sent",
-  "message.delivered",
-  "message.bounced",
-  "message.complained",
-  "domain.verified",
-  "domain.verification_failed",
-  "domain.degraded",
-  "org.reputation_warning",
-  "org.sending_throttled",
-  "org.sending_suspended",
-  "org.reputation_recovered"
-]New value: +[
+  "message.received",
+  "message.sent",
+  "message.delivered",
+  "message.bounced",
+  "message.complained",
+  "mailbox.rule_matched",
+  "domain.verified",
+  "domain.verification_failed",
+  "domain.degraded",
+  "org.reputation_warning",
+  "org.sending_throttled",
+  "org.sending_suspended",
+  "org.reputation_recovered"
+]
    • changedInput schema / properties / events / maxItems
      Previous value: -12New value: +13
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / properties / webhook / properties / events / items / enum
      Previous value: -[
-  "message.received",
-  "message.sent",
-  "message.delivered",
-  "message.bounced",
-  "message.complained",
-  "domain.verified",
-  "domain.verification_failed",
-  "domain.degraded",
-  "org.reputation_warning",
-  "org.sending_throttled",
-  "org.sending_suspended",
-  "org.reputation_recovered"
-]New value: +[
+  "message.received",
+  "message.sent",
+  "message.delivered",
+  "message.bounced",
+  "message.complained",
+  "mailbox.rule_matched",
+  "domain.verified",
+  "domain.verification_failed",
+  "domain.degraded",
+  "org.reputation_warning",
+  "org.sending_throttled",
+  "org.sending_suspended",
+  "org.reputation_recovered"
+]
  2. First observedv0.1.9

TDQS

A3.9/5.0
Behavior4/5

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

The description adds specific behavioral context beyond annotations: changing the URL silently redirects future deliveries. This complements the destructiveHint annotation. No contradiction with annotations.

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?

The description is two sentences, front-loaded with the update action, and the second sentence adds a critical behavioral warning. No redundancy or filler.

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 tool has 6 parameters, an output schema, and many siblings, the description covers the update scope and destructive nature. It lacks prerequisites or auth context, but annotations and schema mitigate these gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions the updatable fields (URL, events, description, active) but adds no additional semantics beyond what the schema provides. With only 33% schema description coverage, the burden is higher, yet the description does not explain formats, constraints, or allowed values.

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?

The description clearly states the tool updates a webhook's URL, events, description, or active state. This distinguishes it from sibling tools like create, delete, get, and rotate secret.

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 description implies when to use the tool (to update webhook properties) but does not provide explicit guidance on when not to use it or contrast with alternatives. The warning about destructive behavior gives context but is not a usage guideline.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shipmail-to/shipmail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server