Skip to main content
Glama
Sign In
AgentSEO MCP Server

AgentSEO MCP Server

by AgentSEO-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

AgentSEO Content Draft QA

agentseo_content_draft_qa
Destructive

Validate a draft URL or Markdown content against live SERP expectations before publishing to catch SEO gaps and improve search readiness.

Instructions

Validate a draft URL or markdown against live SERP expectations before publishing. Uses AgentSEO credits; repeating the call can create new charged work.

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": {
      "keyword": "<keyword>"
    },
    "name": "agentseo_content_draft_qa"
  }
}

Input Schema

NameRequiredDescriptionDefault
syncNoRequest a bounded wait for completion when true. The API can still return a pending job; retain its job ID and poll agentseo_job_status instead of repeating this charged call. False returns a queued job without waiting. Type: Boolean. Default: true.
deviceNoDevice search-result profile used for the analysis. Type: String. Accepted values: "desktop", "mobile". Default: "desktop".desktop
targetNoYour target brand, domain or URL used to scope this workflow; supply the entity you want assessed. Type: String. Optional; no client default.
keywordYesSearch keyword or phrase to analyze for this workflow. Type: String. Required.
languageNoSupported search language code, for example en for English. Type: String. Default: "en".en
locationNoSupported geographic search-market name, for example United States; this is not a coordinate pair. Type: String. Default: "United States".United States
qa_depthNoHow strict the draft quality review should be. Type: String. Accepted values: "standard", "strict". Default: "standard".standard
draft_urlNoAccessible draft or staged web page URL to evaluate; supply this or draft_markdown. Type: String. Format: absolute URL. Optional; no client default.
draft_markdownNoDraft page content as Markdown, used when a draft URL is unavailable; supply this or draft_url. Type: String. Minimum: 100 characters. Maximum: 50000 characters. Optional; no client default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.5
    • addedInput schema / properties / device / description
      Added value: +"Device search-result profile used for the analysis. Type: String. Accepted values: \"desktop\", \"mobile\". Default: \"desktop\"."
    • changedInput schema / properties / draft_markdown / description
      Previous value: -"Draft markdown when no URL exists"New value: +"Draft page content as Markdown, used when a draft URL is unavailable; supply this or draft_url. Type: String. Minimum: 100 characters. Maximum: 50000 characters. Optional; no client default."
    • changedInput schema / properties / draft_url / description
      Previous value: -"Draft or staged page URL"New value: +"Accessible draft or staged web page URL to evaluate; supply this or draft_markdown. Type: String. Format: absolute URL. Optional; no client default."
    • changedInput schema / properties / keyword / description
      Previous value: -"Target keyword"New value: +"Search keyword or phrase to analyze for this workflow. Type: String. Required."
    • addedInput schema / properties / language / description
      Added value: +"Supported search language code, for example en for English. Type: String. Default: \"en\"."
    • addedInput schema / properties / location / description
      Added value: +"Supported geographic search-market name, for example United States; this is not a coordinate pair. Type: String. Default: \"United States\"."
    • addedInput schema / properties / qa_depth / description
      Added value: +"How strict the draft quality review should be. Type: String. Accepted values: \"standard\", \"strict\". Default: \"standard\"."
    • addedInput schema / properties / sync / description
      Added value: +"Request a bounded wait for completion when true. The API can still return a pending job; retain its job ID and poll agentseo_job_status instead of repeating this charged call. False returns a queued job without waiting. Type: Boolean. Default: true."
    • changedInput schema / properties / target / description
      Previous value: -"Optional target brand, domain, or product"New value: +"Your target brand, domain or URL used to scope this workflow; supply the entity you want assessed. Type: String. Optional; no client default."
  2. First observedv0.1.4

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent and open-world behavior, but the description adds cost context that no structured field conveys: credits are consumed and repeating the call can create new charged work. It does not explain what makes the operation 'destructive' per destructiveHint=true, so the disclosure stops short of full transparency.

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?

Two tight sentences, purpose first, billing caveat second, with zero filler. Every clause carries actionable information for the caller.

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 nine-parameter, credit-consuming validation call with no output schema, the definition covers purpose, cost and polling escape hatch. The notable remaining gap is what a validation result actually contains (findings, severity, pass/fail), which the agent must infer.

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 description coverage is 100%, so every parameter including the enum values and the sync polling caveat is documented in the schema. The description only restates the input modality (URL or markdown) without adding semantics beyond the either/or rule already present in the property descriptions.

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?

Names a specific verb and resource: validate a draft URL or markdown against live SERP expectations. The phrase 'before publishing' narrows the intent and the SERP framing partly separates it from siblings like agentseo_content_technical_qa or agentseo_page_cro_qa, though those siblings are never named.

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?

'Before publishing' implies the workflow stage where this belongs, and the sync parameter note routes the agent to agentseo_job_status on a pending job. However, there is no explicit guidance on when to choose this over the adjacent QA tools (technical QA, CRO QA) or on the draft_url vs draft_markdown selection rule beyond what the schema already states.

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

Deploy Server

Other Tools