Skip to main content
Glama

seodraft

by app.seodraft
OverviewDiscussionsAdmin

Create or update draft

upsert_post
Destructive

Create or update a draft. Pass version when updating to avoid overwrites. Cannot mark ready. language is the language this article is written in (2-letter code: "en", "es", "pt") and it is what decides the folder deliver_draft files it under, so it needs to be set whenever the article is not in the workspace profile language, because the profile is only the fallback for drafts that never declared one. Changing it on an article that is linked to a translation is refused when another article in that cluster already covers the new language: unlink first, or fix the other side. brief is the editorial plan and it is saved before the body: intent and template read off the SERP, the angle the SERP does not cover, at least three pieces of first-hand evidence, the H2 outline with the sentence each section opens with, and the image slots the body references as alt. The rules block a draft that has no brief, fewer than three evidence items, or evidence that never reaches the article (get_skill describes the rules). It is separate from serpBrief/customInstructions on get_post, which is the paid Google SERP research.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
bodyNo
dateNo
faqsNo
slugNo
tagsNo
tldrNo
briefNo
titleNo
versionNo
languageNo
descriptionNo
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.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly false, destructive true, non-idempotent). It discloses optimistic-concurrency behavior via version, the refusal condition for language changes on translation-linked articles, that brief is persisted before body, and the validation rules (no brief, <3 evidence items, evidence that never reaches the article).

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-loads the core action, the version guard, and the 'cannot mark ready' constraint before the denser language and brief explanations. Content is information-dense, though the language paragraph is a long run-on chain of clauses that could be tightened.

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 13-parameter, zero-required, nested-object mutation tool with no output schema, it covers the non-obvious semantics, validation blockers, and concurrency risk. Remaining gaps are the unexplained simple scalar fields, which are largely self-describing.

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 8% across 13 parameters, so the description must compensate; it does explain the highest-risk ones (language semantics and folder delivery, brief contents, version). It leaves title/body/slug/tags/date/faqs/tldr/description entirely to name inference, so the compensation is partial.

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 specific verb and resource ('Create or update a draft') plus a hard boundary ('Cannot mark ready'), which implicitly distinguishes it from approve_post. It also names siblings it is not (get_skill, get_post's serpBrief), though it never directly routes to a create-vs-update alternative.

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 concrete operating conditions: pass version when updating, cannot mark ready, set language when the article is not in profile language, unlink first when a linked translation blocks a language change. Exclusions are stated clearly, but no explicit 'use X instead when…' routing across the sibling set.

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