AgentSEO MCP Server

AgentSEO Content Title Meta

agentseo_content_title_meta

Destructive

Generate SEO title and meta description options for a URL or markdown page, using a target keyword and page type to produce alternatives you can compare against existing tags.

Instructions

Generate SEO title and meta description options for a URL or markdown page. 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_title_meta"
  }
}

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`	Yes	Search keyword or phrase to analyze for this workflow. Type: String. Minimum: 1 characters. Required.
`page_type`	No	Page format or classification for this record; select one of the accepted values. Type: String. Accepted values: "auto", "blog_post", "landing_page", "product", "software", "local_business", "comparison_page", "guide". Default: "auto".	auto
`current_title`	No	Existing SEO title to compare with proposed title alternatives. Type: String. Maximum: 120 characters. Optional; no client default.
`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.
`current_meta_description`	No	Existing meta description to compare with proposed alternatives. Type: String. Maximum: 320 characters. Optional; no client default.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.1.5Nov 5, 2026

addedInput schema / properties / current_meta_description / description

Added value: +"Existing meta description to compare with proposed alternatives. Type: String. Maximum: 320 characters. Optional; no client default."

addedInput schema / properties / current_title / description

Added value: +"Existing SEO title to compare with proposed title alternatives. Type: String. Maximum: 120 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. Required."

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\", \"blog_post\", \"landing_page\", \"product\", \"software\", \"local_business\", \"comparison_page\", \"guide\". 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.8/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false, and openWorldHint=true; the description reinforces this by stating it consumes AgentSEO credits and that repeating the call can create new charged work. It does not discuss rate limits, what happens to prior results, or why the operation is destructive, so it adds context without fully exhausting the behavioral picture.

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 with no wasted wording; the core action is front-loaded and the cost caveat follows immediately after.

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 an 8-parameter, no-output-schema tool, the description covers what is generated (title and meta description options) and the credit/repeat risk, which are the two things an agent most needs to know before invoking. It could go slightly further on the URL-vs-markdown choice and on applying the current_title/current_meta_description comparisons, but nothing critical is missing.

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% and each parameter is documented in the schema, including the sync/polling behavior. The description adds only the high-level notion of a URL vs. markdown source and does not explain keyword, page_type, or the current_title/current_meta_description comparison semantics beyond what the schema already says.

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: 'Generate SEO title and meta description options' for 'a URL or markdown page'. That is distinguishable from adjacent siblings like agentseo_content_brief or agentseo_content_draft_qa, though it never names an alternative explicitly.

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?

Usage is implied by the inputs (a URL or a markdown page), and the credit/repeat warning hints at cost sensitivity, but the description never says when to pick this over content_brief, content_refresh_brief, or content_serp_outline, nor any prerequisites such as needing an accessible URL.

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

Deploy Server