AgentSEO MCP Server

AgentSEO Opportunity Brief

agentseo_opportunities_brief

Destructive

Turns a keyword and target domain or page into an implementation-ready SEO brief with opportunity focus, competitor outlines, and next steps.

Instructions

Turn one keyword or page opportunity into an implementation-ready brief. 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>",
      "target": "<target>"
    },
    "name": "agentseo_opportunities_brief"
  }
}

Input Schema

Name	Required	Description	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`	Yes	Target domain, subdomain or absolute page URL to analyze; use a hostname or URL, not a business name. Type: String. Required.
`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
`page_url`	No	Existing target page URL for the opportunity brief, if one already exists. Type: String. Format: absolute URL. Optional; no client default.
`current_rank`	No	Known current organic search position, with 1 meaning first; omit when unknown rather than using zero. Type: Safe integer. Minimum: 1. Maximum: 100. Optional; no client default.
`opportunity_type`	No	Opportunity category to emphasize when constructing the brief. Type: String. Accepted values: "quick_win", "content_refresh", "ai_overview_opportunity", "featured_snippet_opportunity", "commercial_intent_opportunity", "lost_keyword_recovery", "competitor_gap". Optional; no client default.
`include_competitor_outlines`	No	Include sampled competitor heading outlines in the brief when true. Type: Boolean. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.1.5Nov 5, 2026

addedInput schema / properties / current_rank / description

Added value: +"Known current organic search position, with 1 meaning first; omit when unknown rather than using zero. Type: Safe integer. Minimum: 1. Maximum: 100. Optional; no client default."

addedInput schema / properties / include_competitor_outlines / description

Added value: +"Include sampled competitor heading outlines in the brief when true. Type: Boolean. Default: true."

changedInput schema / properties / keyword / description

Previous value: -"Selected opportunity 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 / opportunity_type / description

Added value: +"Opportunity category to emphasize when constructing the brief. Type: String. Accepted values: \"quick_win\", \"content_refresh\", \"ai_overview_opportunity\", \"featured_snippet_opportunity\", \"commercial_intent_opportunity\", \"lost_keyword_recovery\", \"competitor_gap\". Optional; no client default."

addedInput schema / properties / page_url / description

Added value: +"Existing target page URL for the opportunity brief, if one already exists. Type: String. Format: absolute URL. 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."

changedInput schema / properties / target / description

Previous value: -"Target domain or URL"New value: +"Target domain, subdomain or absolute page URL to analyze; use a hostname or URL, not a business name. Type: String. Required."

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 flag this as non-read-only, non-idempotent, destructive and open-world. The description adds genuinely new behavioral context beyond them: it consumes AgentSEO credits and repeating the call can create new charged work. What it doesn't add is what 'destructive' means here or what the produced brief looks like.

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, front-loaded with the core action, followed by the cost caveat. Nothing is redundant and no filler is present.

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 9-parameter, charged, non-idempotent tool with no output schema, the description covers cost and repeat-call risk but says nothing about what the brief actually contains or how to consume it. It also leaves the async path to the parameter description rather than surfacing it, which is a real gap for a paid call.

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 every parameter, including the opportunity_type enum and current_rank bounds, is documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 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 uses a specific verb and resource: turn one keyword or page opportunity into an implementation-ready brief. That is clearly distinct from discovery-oriented siblings like agentseo_opportunities_find, though it never names those siblings explicitly to draw the line.

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 rather than stated: it takes a single opportunity and produces a brief, so an agent can infer it comes after discovery. There is no explicit when-to-use/when-not guidance and no pointer to alternatives such as agentseo_opportunities_find for discovery or agentseo_content_brief for other brief types.

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

Deploy Server