Skip to main content
Glama

Check Draft

check_draft
Read-onlyIdempotent

Runs Mark's content checks on draft text without saving it (six on every channel, two more on a competitor_page, and one more on a website post with a target keyword): exclusion (phrases this workspace blocks or warns on), char_limit, required_meta, ai_fluff (generic AI-sounding words), unsourced_number (percentages, money and multipliers no active claim states), and placeholder (a marker left for the writer, such as [needs source], [TBD] or a bare TODO, ignored inside code, link targets and URLs; it fails). A competitor_page also gets table (a markdown table; it fails, use headings and lists) and open_placeholder (a [confirm: …] fact left to confirm; it fails), and its unsourced_number fails instead of warning. A blog, faq or competitor_page with meta.seo.keyword set also gets keyword (whether seo.title and the body's first paragraph use the target keyword, plurals counted; it only warns, naming each place it is missing). Each result is pass, warn or fail with the matched text, field and position; exclusion matches carry the rule's reason. A fail is what submit_post refuses on a draft; warnings never block. For an X thread, pass assetIds to check each post's media too. On a blog, faq or competitor_page whose post type a CMS maps, required_meta also checks language (pass the post's language): it fails when the CMS collection stores pages per language (get_website_cms localized) and warns otherwise. Uses this workspace's active exclusions and claims. Writes nothing. Related: save_post, get_channel_rules, get_brand_context, list_claims, get_website_cms.

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": {
      "channel": "<channel>",
      "body": "<body>"
    },
    "name": "check_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesDraft body / caption.
metaNoChannel-specific fields from get_channel_rules.
channelYesChannel id such as linkedin or blog.
assetIdsNoX threads: the asset ids save_post would get, so required_meta checks each post's media (4 images, or 1 video, or 1 GIF) with meta.threadMedia.
languageNoWebsite posts: the post's language, a BCP 47 code such as de or de-CH. Omitted or null reads as unset, which fails required_meta when the CMS collection stores pages per language.

Output Schema

NameRequiredDescriptionDefault
checksYesMark's content checks on the saved content: exclusion, char_limit, required_meta, ai_fluff, unsourced_number, placeholder, on a competitor_page also table and open_placeholder, and on a website post with meta.seo.keyword also keyword. On a draft, a fail stops submit_post; warn never does.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 64,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Website posts: the post's language, a BCP 47 code such as de or de-CH. Omitted or null reads as unset, which fails required_meta when the CMS collection stores pages per language."
      +}
  2. Changed2 schema fields changed
    • changedOutput schema / properties / checks / description
      Previous value: -"Mark's content checks on the saved content: exclusion, char_limit, required_meta, ai_fluff, unsourced_number, placeholder, and on a competitor_page also table and open_placeholder. On a draft, a fail stops submit_post; warn never does."New value: +"Mark's content checks on the saved content: exclusion, char_limit, required_meta, ai_fluff, unsourced_number, placeholder, on a competitor_page also table and open_placeholder, and on a website post with meta.seo.keyword also keyword. On a draft, a fail stops submit_post; warn never does."
    • changedOutput schema / properties / checks / items / properties / checkId / enum
      Previous value: -[
      -  "exclusion",
      -  "char_limit",
      -  "required_meta",
      -  "ai_fluff",
      -  "unsourced_number",
      -  "placeholder",
      -  "table",
      -  "open_placeholder"
      -]New value: +[
      +  "exclusion",
      +  "char_limit",
      +  "required_meta",
      +  "ai_fluff",
      +  "unsourced_number",
      +  "placeholder",
      +  "table",
      +  "open_placeholder",
      +  "keyword",
      +  "brand_fit"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / channel / enum
      Previous value: -[
      -  "instagram",
      -  "facebook",
      -  "youtube",
      -  "pinterest",
      -  "tiktok",
      -  "x",
      -  "linkedin",
      -  "linkedin_article",
      -  "blog",
      -  "faq",
      -  "competitor_page",
      -  "landing_page",
      -  "email",
      -  "meta_ads",
      -  "google_ads"
      -]New value: +[
      +  "instagram",
      +  "facebook",
      +  "youtube",
      +  "pinterest",
      +  "tiktok",
      +  "x",
      +  "linkedin",
      +  "linkedin_article",
      +  "blog",
      +  "faq",
      +  "competitor_page",
      +  "meta_ads",
      +  "google_ads"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / channel / enum
      Previous value: -[
      -  "instagram",
      -  "facebook",
      -  "youtube",
      -  "pinterest",
      -  "tiktok",
      -  "x",
      -  "linkedin",
      -  "blog",
      -  "faq",
      -  "competitor_page",
      -  "landing_page",
      -  "email",
      -  "meta_ads",
      -  "google_ads"
      -]New value: +[
      +  "instagram",
      +  "facebook",
      +  "youtube",
      +  "pinterest",
      +  "tiktok",
      +  "x",
      +  "linkedin",
      +  "linkedin_article",
      +  "blog",
      +  "faq",
      +  "competitor_page",
      +  "landing_page",
      +  "email",
      +  "meta_ads",
      +  "google_ads"
      +]
  5. Changed2 schema fields changed
    • changedOutput schema / properties / checks / description
      Previous value: -"Mark's content checks on the saved content: exclusion, char_limit, required_meta, ai_fluff, unsourced_number, placeholder. On a draft, a fail stops submit_post; warn never does."New value: +"Mark's content checks on the saved content: exclusion, char_limit, required_meta, ai_fluff, unsourced_number, placeholder, and on a competitor_page also table and open_placeholder. On a draft, a fail stops submit_post; warn never does."
    • changedOutput schema / properties / checks / items / properties / checkId / enum
      Previous value: -[
      -  "exclusion",
      -  "char_limit",
      -  "required_meta",
      -  "ai_fluff",
      -  "unsourced_number",
      -  "placeholder"
      -]New value: +[
      +  "exclusion",
      +  "char_limit",
      +  "required_meta",
      +  "ai_fluff",
      +  "unsourced_number",
      +  "placeholder",
      +  "table",
      +  "open_placeholder"
      +]
  6. Changed1 schema field changed
    • addedInput schema / properties / assetIds
      Added value: +{
      +  "description": "X threads: the asset ids save_post would get, so required_meta checks each post's media (4 images, or 1 video, or 1 GIF) with meta.threadMedia.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 100,
      +  "type": "array"
      +}
  7. Changed2 schema fields changed
    • changedOutput schema / properties / checks / description
      Previous value: -"Mark's content checks on the saved content: exclusion, char_limit, required_meta, ai_fluff, unsourced_number. On a draft, a fail stops submit_post; warn never does."New value: +"Mark's content checks on the saved content: exclusion, char_limit, required_meta, ai_fluff, unsourced_number, placeholder. On a draft, a fail stops submit_post; warn never does."
    • changedOutput schema / properties / checks / items / properties / checkId / enum
      Previous value: -[
      -  "exclusion",
      -  "char_limit",
      -  "required_meta",
      -  "ai_fluff",
      -  "unsourced_number"
      -]New value: +[
      +  "exclusion",
      +  "char_limit",
      +  "required_meta",
      +  "ai_fluff",
      +  "unsourced_number",
      +  "placeholder"
      +]
  8. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, so the description correctly spends its budget elsewhere: the pass/warn/fail grading, which severities block submit_post, and the fact that unsourced_number escalates from warn to fail on competitor_page. It also discloses that checks run against live workspace rules, which matters for reproducibility.

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 action and scope, then progressively discloses per-channel deltas. The single dense paragraph is heavy to scan and repeats the 'it fails' verdict three times, but nearly every clause carries unique behavioral information rather than filler.

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?

An output schema exists, so the description needn't explain return shape, and instead covers what an agent actually needs: per-channel check sets, severity semantics, prerequisites, and the escalation path to submit_post. Nothing material is missing for a 5-parameter validation tool.

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 schema baseline is already a 3. The description goes further by tying assetIds to X threads (with meta.threadMedia expectations) and language to CMS-localized collections, giving the agent the conditional logic behind each optional parameter rather than just its type.

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 ('Runs Mark's content checks on draft text without saving it'), then enumerates the exact checks and how they vary by channel. The 'without saving it' clause separates it cleanly from save_post and submit_post in the sibling list.

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 preconditions ('Uses this workspace's active exclusions and claims', meta fields come from get_channel_rules, and 'A fail is what submit_post refuses on a draft'), plus the related-tools list. It never states an explicit 'do not use for X' exclusion, but the caller knows exactly what state the tool depends on and what to do with the result.

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