Skip to main content
Glama

Unpublish a lead magnet

unpublish_lead_magnet
DestructiveIdempotent

Take a live lead magnet off the public Library. 'pause' (default) keeps its page saying it is unavailable; 'draft' returns it to a private draft. The ebook, the PDF, the leads and the numbers are all kept, and publish_lead_magnet puts it back at the same address.

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": {
      "magnetId": "<magnetId>"
    },
    "name": "unpublish_lead_magnet"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNopause: the page says it is unavailable (default). draft: back to a private draft. Either way the ebook, leads and numbers are kept.pause
magnetIdYesFrom list_lead_magnets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the context that matters most: the ebook, PDF, leads and numbers are kept and the magnet can be restored at the same address, which reframes the destructive flag as a visibility change rather than data loss. It does not state any permission requirements, but it does much more than repeat the annotations and does not contradict them.

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?

Three short sentences, front-loaded with the action, then the mode distinction, then the retention and reversal guarantee. Every sentence carries information an agent needs and there is no 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?

For a two-parameter state-change tool with no output schema, the description covers the side effect, the mode semantics, data retention, and the reversal path. Nothing an agent needs in order to invoke it 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?

Schema description coverage is 100%, and the schema's mode description is essentially identical to the sentence in the description, so the description adds no meaning beyond what the schema already documents. The magnetId provenance ("From list_lead_magnets") also lives in the schema. Baseline 3 applies.

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 ("Take a live lead magnet off the public Library") and implicitly contrasts with the inverse operation, so the agent knows exactly what changes in the world. It is clearly distinguishable from publish_lead_magnet, which is named explicitly.

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?

Establishes the precondition that the magnet must be live and names publish_lead_magnet as the way back, giving a clear when-to-use context. It stops short of explicitly ruling out related operations such as update_lead_magnet when the intent is only to hide rather than edit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources