Skip to main content
Glama

Reschedule or edit a scheduled publication or draft

update_publication
Idempotent

Change a publication that is still scheduled or a draft. update.scheduledFor (ISO 8601 with an offset) reschedules it, and turns a draft into a scheduled publication; update.timeZone records the zone it was chosen in. update.platforms, with optional content and media, replaces the whole post, validated like create_publication. Fails once the publication has started.

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": {
      "publicationId": "<publicationId>",
      "update": "<update>"
    },
    "name": "update_publication"
  }
}

Input Schema

NameRequiredDescriptionDefault
updateYes
publicationIdYesA publication id from create_publication or list_publications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description adds genuinely new context, notably that platforms replaces the whole post and that the call fails once publishing has started. It does not explain what error surfaces on that failure, what permissions are required, or whether omitted fields are left untouched (only implied by the replacement wording).

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?

Four tight sentences, front-loaded with the eligibility rule, then the reschedule path, then the replacement path, then the failure condition. No filler and no restatement of the name or title.

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?

For a two-parameter tool with a deeply nested update object, this covers eligibility, both mutation modes, and the hard failure boundary. The one remaining ambiguity is whether omitting update.platforms leaves the existing post intact, which an agent must infer from 'replaces the whole post'.

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

Parameters4/5

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

Schema coverage is 50%, and the description compensates well: it explains that scheduledFor both reschedules and promotes a draft, why timeZone exists, and that platforms is a full replacement validated like create_publication. Gaps remain on the nested kind/options fields and the count limits (20 platforms, 35 media).

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 plus the scope precondition: 'Change a publication that is still scheduled or a draft.' That precondition alone separates it from publish_publication and cancel_publication without needing to name them.

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?

Gives a clear when-not ('Fails once the publication has started') and routes validation semantics to create_publication, so the agent knows the editing surface matches creation. It stops short of explicit alternatives for the other lifecycle states (cancelling or publishing), leaving that routing to inference.

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