Skip to main content
Glama

Schedule a future article

schedule_article

Schedule a topic to be generated and auto-published on WordPress, or Framer/Webflow connected with an API token or key. Italian translation is WordPress-only. Framer publishing deploys the whole project. Requires a plan with scheduling enabled.

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": {
      "topic": "<topic>",
      "siteId": "<siteId>",
      "scheduledFor": "<scheduledFor>"
    },
    "name": "schedule_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes
siteIdYes
dualLanguageNoAlso publish an Italian translation alongside the original
scheduledForYesISO 8601 date-time in the future, e.g. 2026-08-01T09:00:00Z
publishStatusNopublish

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already flag a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description adds genuinely useful traits beyond that: a plan entitlement prerequisite and the notable side effect that Framer publishing deploys the whole project. It does not address the idempotentHint=false implication (whether rescheduling the same topic creates duplicates) or what happens if scheduledFor is in the past despite the schema constraint.

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?

Three short sentences with no filler, front-loading the action and platform scope before the constraints. Slightly dense with platform caveats but every clause carries decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-idempotent creation tool with no output schema and five parameters at 40% coverage, the description is adequate but not complete. It omits the draft/publishStatus semantics and gives no indication of the return value or timezone handling for scheduledFor, gaps an agent would want filled.

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 only 40%, so the description must compensate, and it partly does: it clarifies that dualLanguage is WordPress-only, adding real meaning beyond the schema's own description of that field, and reinforces the future-dating of scheduledFor. It never mentions publishStatus, so the draft versus publish choice (default publish) is unexplained, leaving a fifth of the interface undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (schedule) applied to a specific resource (a topic that will be generated and auto-published) and scopes the targets to WordPress or Framer/Webflow sites with an API token or key. That is far more informative than the title alone. It stops short of naming the boundary against publish_article or generate_article, so an agent must infer that 'scheduled' means future-dated rather than immediate.

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

Usage Guidelines3/5

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

A real prerequisite is disclosed: 'Requires a plan with scheduling enabled.' Platform exclusions are also implied (Italian translation only on WordPress). However, there is no explicit when-to-use versus publish_article or generate_article, and no guidance on what to do if the plan lacks scheduling.

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