Skip to main content
Glama

seodraft

by app.seodraft
OverviewDiscussionsAdmin

Unschedule post

unschedule_post
DestructiveIdempotent

Take an article off the calendar without retiring it: status goes back to writing and the calendar day is freed for planning. The body, tldr, FAQs and brief are kept untouched. This is the inverse of schedule_entry, not a delete. Refuses with degraded reason not-scheduled when the article is not scheduled but still holds a day (move it with reschedule_post instead), and already-unscheduled when it is already a dateless draft. To retire an article instead, use archive_post.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
workspaceIdNoThe workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
+  "description": "The workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag this as a non-read-only, destructive, idempotent mutation, but the description adds what the annotations cannot: the exact state transition (status back to writing, calendar day freed), what is preserved (body, tldr, FAQs, brief), and two named degraded-reason error codes for refusal. That is substantive behavioral disclosure beyond structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core effect before the sibling routing and error cases, and every sentence carries information. Slightly dense as a single unbroken block, but there is no filler to cut.

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 2-param mutation tool with no output schema, the definition covers state change, data preservation, refusal conditions, and sibling alternatives. Annotations cover the safety profile, so nothing an agent needs in order to invoke this 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 coverage is 50%: workspaceId is fully documented in the schema, while id is undocumented there and only implied by the description's references to 'the article'. The description adds no syntax, format, or fallback detail for the id parameter, so it neither compensates for nor worsens the coverage gap.

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 precise verb+resource (take an article off the calendar) and immediately disambiguates against three siblings: schedule_entry (inverse), reschedule_post (for the held-day case), and archive_post (for retiring). An agent can pick correctly without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use and when-not-to-use, including the two refusal conditions (not-scheduled when a day is still held, already-unscheduled when a dateless draft) with the correct alternative named for each case.

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

All seodraft toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources