Skip to main content
Glama
Sign In
shipmail-mcp

shipmail-mcp

by shipmail-to
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Revoke Audience Feed URLs

shipmail_revoke_audience_feed
DestructiveIdempotent

Disable an audience's current and previous feed URLs instantly. Returns a replacement feed URL, forcing existing readers to subscribe again.

Instructions

Immediately disable the current and every previous feed URL, then return a replacement. Existing readers must subscribe again.

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_revoke_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

A3.8/5.0
Behavior4/5

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

Description adds important behavioral details beyond annotations: 'Immediately disable the current and every previous feed URL' (confirms destructive hint) and 'Existing readers must subscribe again' (new behavioral context). No contradictions with annotations 'destructiveHint=true' and 'idempotentHint=true'.

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, front-loaded with the main action, no fluff. Every sentence adds value: first states the effect, second the consequence for users.

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 presence of annotations (idempotent, destructive hints) and an output schema (not shown but exists), the description covers the key behavioral effect and result (replacement URL). Could briefly mention that the operation returns the new feed URL, but completeness is adequate.

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 descriptions for both parameters (audience_id, idempotency_key). The description adds no extra meaning about parameters, so baseline score of 3 is appropriate.

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 title 'Revoke Audience Feed URLs' and description clearly state the action (disable all previous feed URLs and return a replacement), distinguishing it from siblings like 'rotate_audience_feed' by emphasizing that previous URLs are invalidated.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like 'rotate_audience_feed' or 'update_audience_feed'. The description implies invalidation of all previous feeds but does not compare or contrast with sibling tools.

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