AgentSEO MCP Server

AgentSEO Content Refresh Brief

agentseo_content_refresh_brief

Destructive

Generate a refresh brief for an existing URL and keyword to guide SEO content updates and compare page outlines by heading depth.

Instructions

Create a refresh brief for an existing URL and keyword. 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": {
      "url": "<url>",
      "keyword": "<keyword>"
    },
    "name": "agentseo_content_refresh_brief"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Absolute web page URL to analyze; use an http:// or https:// URL. Type: String. Format: absolute URL. Required.
`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.
`keyword`	Yes	Search keyword or phrase to analyze for this workflow. Type: String. Required.
`language`	No	Supported search language code, for example en for English. Type: String. Default: "en".	en
`location`	No	Supported geographic search-market name, for example United States; this is not a coordinate pair. Type: String. Default: "United States".	United States
`scrape_depth`	No	Deepest heading level to include when comparing scraped page outlines. Type: String. Accepted values: "h1", "h2", "h3". Default: "h3".	h3

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.1.5Nov 5, 2026

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 / scrape_depth / description

Added value: +"Deepest heading level to include when comparing scraped page outlines. Type: String. Accepted values: \"h1\", \"h2\", \"h3\". Default: \"h3\"."

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 / url / description

Previous value: -"Existing page URL"New value: +"Absolute web page URL to analyze; use an http:// or https:// URL. Type: String. Format: absolute URL. Required."

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 declare this as a non-readonly, non-idempotent, destructive, open-world operation. The description adds important context beyond that: it uses AgentSEO credits and repeating the call can create new charged work, which directly clarifies cost and non-idempotency behavior.

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?

The description is two tight sentences with no filler. The purpose is front-loaded and the cost warning follows immediately, so every sentence carries useful information.

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 charged, non-idempotent job-creation tool with no output schema, the description covers purpose and the key cost/repeat-call risk. Details about sync behavior and polling are handled by the schema's sync parameter, so the description does not need to repeat them.

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 all six parameters, including sync, language, location, and scrape_depth. The description adds no parameter-level meaning beyond mentioning the existing URL and keyword inputs.

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: 'Create a refresh brief for an existing URL and keyword.' The 'refresh' and 'existing URL' wording gives useful scope, but it does not explicitly differentiate this from sibling tools such as agentseo_content_brief or agentseo_content_action_plan.

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?

The existing-URL and keyword scope implies a use case, but the description does not state when to choose this tool over alternatives or when not to use it. There is no routing guidance among the many content-related siblings.

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

Deploy Server