Skip to main content
Glama
Sign In
shipmail-mcp

shipmail-mcp

by shipmail-to
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Rotate Audience Feed URL

shipmail_rotate_audience_feed
DestructiveIdempotent

Rotate an audience feed URL to generate a replacement, redirecting current traffic to the new URL and permanently deactivating the oldest one.

Instructions

Generate a replacement feed URL. The current URL redirects to it until the next rotation, which permanently breaks the oldest URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "audience_id": "<audience_id>"
    },
    "name": "shipmail_rotate_audience_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
audience_idYesAudience ID.
idempotency_keyNoOptional idempotency key. If omitted, the MCP server generates one for POST tools.

Output Schema

NameRequiredDescriptionDefault
feedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.10

TDQS

A4.3/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations: 'which permanently breaks the oldest URL' aligns with destructiveHint, and 'The current URL redirects to it until the next rotation' explains the redirection. This provides useful transparency without contradicting 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?

Two sentences, zero waste. The first sentence states the main action, and the second explains the behavior. Front-loaded and efficient.

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?

Given the presence of annotations (idempotentHint, destructiveHint) and an output schema, the description is complete. It captures the key behavioral nuance about breaking the oldest URL, which is essential for the agent to understand the tool's effect.

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 coverage is 100%, with 'audience_id' and 'idempotency_key' already described in the schema. The description does not add extra meaning or usage context for parameters, so it meets the baseline for high coverage but does not improve it.

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 'Generate a replacement feed URL' and explains the rotation mechanism, distinguishing it from sibling tools like get_audience_feed, update_audience_feed, and revoke_audience_feed. The verb 'generate' and resource 'feed URL' are specific.

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

Usage Guidelines4/5

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

The description implies when to use: to rotate the feed URL. It explains that the current URL redirects to the new one until the next rotation, which permanently breaks the oldest URL. However, it does not explicitly state when not to use or mention alternatives, but the context is clear.

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