AgentSEO MCP Server

AgentSEO Content Action Plan

agentseo_content_action_plan

Destructive

Convert supplied SEO opportunities into a capacity-aware content calendar and execution plan, prioritizing work by goal, effort, and weekly capacity.

Instructions

Turn supplied SEO opportunities into a capacity-aware content calendar and execution plan. 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": {
      "items": "<items>"
    },
    "name": "agentseo_content_action_plan"
  }
}

Input Schema

Name	Required	Description	Default
`goal`	No	Primary business outcome used to prioritize the proposed content plan. Type: String. Accepted values: "traffic_growth", "lead_generation", "refresh_decay", "launch_support", "authority_building". Default: "traffic_growth".	traffic_growth
`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.
`team`	No	Team member or role labels available for assignment in the plan; use roles instead of personal details when possible. Type: Array. Maximum: 20 items. Default: [].
`items`	Yes	Supplied opportunities or tasks to prioritize and schedule; this creates a plan, not CMS posts or calendar events. Type: Array. Minimum: 1 items. Maximum: 100 items. Required.
`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.
`start_date`	No	Planning start date in YYYY-MM-DD calendar-date format; omit to let the service choose a start date. Type: String. Format must match /^\d{4}-\d{2}-\d{2}$/. Optional; no client default.
`horizon_days`	No	Planning horizon measured in calendar days. Type: Safe integer. Minimum: 7. Maximum: 90. Default: 30.
`weekly_capacity`	No	Weekly planning capacity in effort points, not hours or item count. Small tasks use 1 point, medium 2 and large 4; overflow can be placed in the final planning week. Type: Safe integer. Minimum: 1. Maximum: 25. Default: 5.

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedv0.1.5Nov 5, 2026

addedInput schema / properties / goal / description

Added value: +"Primary business outcome used to prioritize the proposed content plan. Type: String. Accepted values: \"traffic_growth\", \"lead_generation\", \"refresh_decay\", \"launch_support\", \"authority_building\". Default: \"traffic_growth\"."

addedInput schema / properties / horizon_days / description

Added value: +"Planning horizon measured in calendar days. Type: Safe integer. Minimum: 7. Maximum: 90. Default: 30."

addedInput schema / properties / items / description

Added value: +"Supplied opportunities or tasks to prioritize and schedule; this creates a plan, not CMS posts or calendar events. Type: Array. Minimum: 1 items. Maximum: 100 items. Required."

addedInput schema / properties / items / items / description

Added value: +"One supplied opportunity or work item to prioritize. Type: Object. Required."

addedInput schema / properties / items / items / properties / buyer_stage / description

Added value: +"Buyer-journey stage associated with this page or opportunity. Type: String. Accepted values: \"awareness\", \"consideration\", \"decision\", \"implementation\", \"retention\". Default: \"awareness\"."

addedInput schema / properties / items / items / properties / dependencies / description

Added value: +"Names or labels of prerequisite work items that should be completed first. Type: Array. Maximum: 10 items. Default: []."

addedInput schema / properties / items / items / properties / dependencies / items / description

Added value: +"One prerequisite work-item title or label. Type: String. Minimum: 1 characters. Maximum: 160 characters. Required."

addedInput schema / properties / items / items / properties / effort / description

Added value: +"Relative planning effort: small uses 1 capacity point, medium 2 and large 4; these are not hours. Type: String. Accepted values: \"small\", \"medium\", \"large\". Default: \"medium\"."

addedInput schema / properties / items / items / properties / impact_score / description

Added value: +"Supplied impact score on a 0-100 scale, with larger values indicating greater expected impact. Type: Number. Minimum: 0. Maximum: 100. Optional; no client default."

addedInput schema / properties / items / items / properties / keyword / description

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

addedInput schema / properties / items / items / properties / notes / description

Added value: +"Additional supplied context relevant to this record; exclude credentials and unnecessary personal data. Type: String. Maximum: 1000 characters. Optional; no client default."

addedInput schema / properties / items / items / properties / opportunity_type / description

Added value: +"Kind of planned SEO work used to prioritize and route this item. Type: String. Accepted values: \"new_content\", \"refresh\", \"technical_fix\", \"internal_links\", \"schema\", \"backlink_outreach\", \"monitoring\". Default: \"new_content\"."

addedInput schema / properties / items / items / properties / priority / description

Added value: +"Supplied urgency level used when ordering the work. Type: String. Accepted values: \"low\", \"medium\", \"high\", \"critical\". Default: \"medium\"."

addedInput schema / properties / items / items / properties / source_endpoint / description

Added value: +"AgentSEO API path that produced the opportunity, for example /content/gap; provenance only, not an endpoint to execute. Type: String. Maximum: 120 characters. Optional; no client default."

addedInput schema / properties / items / items / properties / status / description

Added value: +"Current workflow state of the supplied work item. Type: String. Accepted values: \"idea\", \"ready\", \"blocked\", \"in_progress\". Default: \"idea\"."

addedInput schema / properties / items / items / properties / title / description

Added value: +"Title of the supplied page or work item, used as its human-readable label. Type: String. Minimum: 1 characters. Maximum: 180 characters. Required."

addedInput schema / properties / items / items / properties / url / description

Added value: +"Absolute URL of the page associated with this planned work item; provenance only, not a fetch or publish request. Type: String. Format: absolute URL. Optional; no client default."

addedInput schema / properties / start_date / description

Added value: +"Planning start date in YYYY-MM-DD calendar-date format; omit to let the service choose a start date. Type: String. Format must match /^\\d{4}-\\d{2}-\\d{2}$/. Optional; no client default."

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

Added value: +"Team member or role labels available for assignment in the plan; use roles instead of personal details when possible. Type: Array. Maximum: 20 items. Default: []."

addedInput schema / properties / team / items / description

Added value: +"One available team role or member label for planning assignments. Type: String. Minimum: 1 characters. Maximum: 80 characters. Required."

addedInput schema / properties / weekly_capacity / description

Added value: +"Weekly planning capacity in effort points, not hours or item count. Small tasks use 1 point, medium 2 and large 4; overflow can be placed in the final planning week. Type: Safe integer. Minimum: 1. Maximum: 25. Default: 5."

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 declare destructiveHint=true and idempotentHint=false, and the description adds context the annotations cannot express: the call consumes AgentSEO credits and repeating it creates new charged work. That is a genuinely useful behavioral disclosure for a non-idempotent, capacity-consuming operation. It stops short of saying what planning output is produced or that a pending job may need polling, though the sync parameter covers the latter.

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, zero filler. The output artifact comes first and the cost caveat follows immediately, so both key facts are front-loaded.

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?

With annotations covering safety and a fully described 8-parameter schema plus a nested items object, the description only needs to add the credit/non-idempotency warning, which it does. The remaining gap is the absence of any sibling routing, which matters given how many adjacent content-planning tools exist.

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 is documented in the schema, including the effort-point semantics and the weekly_capacity overflow rule. The description adds no parameter meaning of its own beyond the phrase 'capacity-aware', so the baseline 3 is appropriate.

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 output artifact: turn supplied SEO opportunities into a capacity-aware content calendar and execution plan. That is concrete and distinguishable from drafting tools, but it never names or contrasts with close siblings such as agentseo_opportunities_brief or agentseo_content_brief, which an agent would need to choose correctly.

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 only implied: it assumes the caller already has 'supplied SEO opportunities' in hand. The caution about repeating the call is a cost warning, not a when-to-use rule, and there is no statement of when to prefer this over the brief or gap tools in the sibling list.

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

Deploy Server