Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Create Draft Tool

adataforseo.create_draft

Creates an unpublished draft page for a missing target under a chosen parent, with permission checks; use preview to review the proposed title, alias, and parent before applying.

Instructions

Changes the site. Creates an unpublished document for a missing target page, under the chosen parent, with the manager page permission checks. Returns change ids for adataforseo.undo_change. Set preview to true to see the proposed title, alias and parent first.

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": {
      "target": "<target>"
    },
    "name": "adataforseo.create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentNoParent document id; 0 (the default) creates at the site root
targetYesMissing target id from adataforseo.matrix
previewNoOnly show the changes
pagetitleNoOverride the generated page title

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A4.3/5.0
Behavior5/5

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

With only readOnlyHint=false supplied, the description carries real weight: it discloses that this mutates the site, that the result is unpublished, that manager page permission checks apply, that change ids are returned for adataforseo.undo_change (reversibility), and that preview mode is non-committal. That is exactly the behavioral context annotations cannot provide.

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 short sentences, front-loaded with the mutation ('Changes the site'), then the creation semantics, the return value, and the preview recommendation. No sentence is redundant.

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 four-parameter mutation tool with no output schema, the definition covers effect, permissions, reversal path and preview. It stops short of explaining behavior when the target is not actually missing or how permissions failures surface, but nothing critical to a correct call is absent.

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 100%, so the baseline is 3; the description goes slightly beyond it by explaining that preview reveals the proposed title, alias and parent rather than merely 'showing changes'. The pagetitle override is left to the schema, which is acceptable given full coverage.

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?

States a concrete verb and resource ('Creates an unpublished document for a missing target page') and ties the input to adataforseo.matrix, so an agent knows this writes a draft page rather than applying a fix. It does not explicitly contrast itself with adataforseo.apply_fix, which is the nearest competing write operation, so it stops just short of full sibling differentiation.

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?

The phrase 'for a missing target page' acts as an entry condition, and 'Set preview to true to see the proposed title, alias and parent first' prescribes a safe workflow. There is no explicit when-not guidance, e.g. what to do if the target page already exists, but the usage context is clear.

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