AgentSEO MCP Server

AgentSEO Content Schema Plan

agentseo_content_schema_plan

Destructive

Plan JSON-LD schema recommendations for a URL or Markdown page without a provider call, generating structured-data proposals you can review before publishing.

Instructions

Plan JSON-LD schema for a URL or markdown page without a provider call. 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_schema_plan"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Absolute web page URL to analyze; use an http:// or https:// URL. Type: String. Format: absolute URL. Optional; no client default.
`sync`	No	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.
`target`	No	Your target brand, domain or URL used to scope this workflow; supply the entity you want assessed. Type: String. Optional; no client default.
`keyword`	No	Search keyword or phrase to analyze for this workflow. Type: String. Optional; no client default.
`page_type`	No	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", "faq", "how_to". Default: "auto".	auto
`page_markdown`	No	Page content supplied as Markdown instead of fetching url; provide page content or an accessible URL. Type: String. Minimum: 80 characters. Maximum: 50000 characters. Optional; no client default.
`include_jsonld`	No	Include proposed JSON-LD structured-data examples in the plan when true; this does not publish them. Type: Boolean. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.1.5Nov 5, 2026

addedInput schema / properties / include_jsonld / description

Added value: +"Include proposed JSON-LD structured-data examples in the plan when true; this does not publish them. Type: Boolean. Default: true."

addedInput schema / properties / keyword / description

Added value: +"Search keyword or phrase to analyze for this workflow. Type: String. Optional; no client default."

changedInput schema / properties / page_markdown / description

Previous value: -"Page markdown when no URL exists"New value: +"Page content supplied as Markdown instead of fetching url; provide page content or an accessible 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\", \"faq\", \"how_to\". 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."

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."

changedInput schema / properties / url / description

Previous value: -"Page URL to scrape"New value: +"Absolute web page URL to analyze; use an http:// or https:// URL. Type: String. Format: absolute URL. Optional; no client default."

First observedv0.1.4Nov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare non-readOnly, non-idempotent, destructive, and openWorld, and the description adds real context on top: it consumes AgentSEO credits and re-invocation can spawn new charged work. It does not quantify cost or explain what the destructiveHint implies for a "plan" operation, which leaves a small gap.

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 short sentences, both load-bearing: the first defines the operation and its no-provider characteristic, the second warns about credit consumption and repeat charges. Nothing is redundant or buried.

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 seven-parameter paid tool with no output schema, the description omits what a "plan" actually returns (proposed JSON-LD shapes, validation notes?) and never states that at least one of url or page_markdown must be supplied. The credit/idempotency warning is useful but does not fully compensate.

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 the schema already documents url, sync, target, keyword, page_type, page_markdown, and include_jsonld in detail. The description only restates the url-or-markdown input choice and adds no new semantics about parameter interplay.

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 states a specific verb and resource: "Plan JSON-LD schema for a URL or markdown page," and adds the differentiator "without a provider call." It does not name a sibling tool it is distinguished from, even though the catalog contains adjacent content tools (e.g., agentseo_content_technical_qa, agentseo_extract), so an agent must infer the boundary.

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?

"Without a provider call" implies this is the cheaper, purely generative option, and the credit warning implies a when-not (don't repeat). But there is no explicit statement of when to choose this over sibling content-planning tools, nor any prerequisite such as requiring either url or page_markdown.

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

Deploy Server