Skip to main content
Glama
Sign In
AgentSEO MCP Server

AgentSEO MCP Server

by AgentSEO-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

AgentSEO Content Technical QA

agentseo_content_technical_qa
Destructive

Run pre-publish SEO QA on a page to verify metadata, indexability, canonical tags, headings, schema, links, and media before publishing.

Instructions

Run pre-publish SEO QA for metadata, indexability, canonical, headings, schema, links, and media. Uses AgentSEO credits; repeating the call can create new charged work.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agentseo_content_technical_qa"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoAbsolute web page URL to analyze; use an http:// or https:// URL. Type: String. Format: absolute URL. Optional; no client default.
htmlNoPage HTML supplied directly for analysis; provide this, markdown or a URL and avoid secrets in markup. Type: String. Minimum: 80 characters. Maximum: 250000 characters. Optional; no client default.
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.
targetNoYour target brand, domain or URL used to scope this workflow; supply the entity you want assessed. Type: String. Optional; no client default.
keywordNoSearch keyword or phrase to analyze for this workflow. Type: String. Minimum: 1 characters. Optional; no client default.
markdownNoPage Markdown supplied directly for analysis; provide this, html or a URL. Type: String. Minimum: 80 characters. Maximum: 50000 characters. Optional; no client default.
page_typeNoPage format or classification for this record; select one of the accepted values. Type: String. Accepted values: "auto", "article", "blog_post", "landing_page", "product", "software", "local_business", "comparison_page", "guide", "docs". Default: "auto".auto
expected_canonicalNoAbsolute canonical URL the page should declare, used as the comparison target. Type: String. Format: absolute URL. Optional; no client default.
check_external_linksNoExternal-link review preference. The current workflow inspects extracted link information, not the HTTP status of every external destination; fetching the source url can still access the internet. Type: Boolean. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.5
    • addedInput schema / properties / check_external_links / description
      Added value: +"External-link review preference. The current workflow inspects extracted link information, not the HTTP status of every external destination; fetching the source url can still access the internet. Type: Boolean. Default: false."
    • addedInput schema / properties / expected_canonical / description
      Added value: +"Absolute canonical URL the page should declare, used as the comparison target. Type: String. Format: absolute URL. Optional; no client default."
    • addedInput schema / properties / html / description
      Added value: +"Page HTML supplied directly for analysis; provide this, markdown or a URL and avoid secrets in markup. Type: String. Minimum: 80 characters. Maximum: 250000 characters. Optional; no client default."
    • addedInput schema / properties / keyword / description
      Added value: +"Search keyword or phrase to analyze for this workflow. Type: String. Minimum: 1 characters. Optional; no client default."
    • addedInput schema / properties / markdown / description
      Added value: +"Page Markdown supplied directly for analysis; provide this, html or a URL. Type: String. Minimum: 80 characters. Maximum: 50000 characters. Optional; no client default."
    • addedInput schema / properties / page_type / description
      Added value: +"Page format or classification for this record; select one of the accepted values. Type: String. Accepted values: \"auto\", \"article\", \"blog_post\", \"landing_page\", \"product\", \"software\", \"local_business\", \"comparison_page\", \"guide\", \"docs\". Default: \"auto\"."
    • 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."
    • addedInput schema / properties / target / description
      Added value: +"Your target brand, domain or URL used to scope this workflow; supply the entity you want assessed. Type: String. Optional; no client default."
    • addedInput schema / properties / url / description
      Added value: +"Absolute web page URL to analyze; use an http:// or https:// URL. Type: String. Format: absolute URL. Optional; no client default."
  2. First observedv0.1.4

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag this as non-read-only, non-idempotent, open-world, and destructive, so the bar is lower. The description still adds real value annotations cannot express: the call consumes AgentSEO credits and repeating it can generate new charged work, which concretely explains the idempotentHint=false and destructiveHint=true for the agent.

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 sentences, the capability stated first and the cost hazard second. Nothing is padded and the most decision-relevant warning is front-loaded within the second clause.

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 nine-parameter destructive tool with no output schema, the description is reasonably complete on cost behavior but omits the key input constraint that at least one of url, html, or markdown must be supplied — every parameter is individually marked optional, so an agent could attempt a source-less call. It also does not describe the shape of the QA result, which the absence of an output schema leaves unaddressed.

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 all nine parameters are already documented with types, formats, defaults, and the enum for page_type. The description adds no parameter-level detail at all, so the baseline of 3 applies.

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 names a specific verb and resource ('Run pre-publish SEO QA') and enumerates the exact check surface: metadata, indexability, canonical, headings, schema, links, media. That enumeration is what separates it from siblings like agentseo_page_cro_qa or agentseo_content_draft_qa, though no sibling is named outright.

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?

'Pre-publish' establishes timing, which implicitly scopes usage to content before it goes live. However, there is no explicit when-not guidance, no named alternative for post-publish auditing, and no mention of routing pending jobs to agentseo_job_status (that appears only in the schema's sync description).

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