Skip to main content
Glama

Resume Page Publishing

resume_page_publishing
Destructive

Resume a page campaign whose publishing was PAUSED BY THE SCALE GOVERNOR (list_seo_campaigns shows publishingHold on the campaign: the first published pages earned essentially no Google search appearances, so the drip stopped itself before publishing more of the same template). Resuming is an explicit, informed decision: pass the resumeToken from that hold - the token is derived from the hold itself, so having it proves the evidence was read. STRONGLY consider fixing the template/content first (the hold says why the pages aren't being found); resuming publishes more of what is currently not working. Cost: resuming is free, but the released pages bill AI credits as each one generates/publishes (same as campaign execution).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesThe held campaign id
resumeTokenYesThe hold's resumeToken from list_seo_campaigns.publishingHold

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / user_intent
      Removed value: -{
      -  "description": "Optional: one short sentence describing what the user is ultimately trying to achieve with this request. Used by SEOmatic to tailor answers and improve the product; never required.",
      -  "maxLength": 300,
      -  "type": "string"
      -}
  2. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.