Skip to main content
Glama
Sign In
AgentSEO MCP Server

AgentSEO MCP Server

by AgentSEO-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

AgentSEO Opportunity Finder

agentseo_opportunities_find
Destructive

Find prioritized SEO opportunities for a domain or URL by analyzing keyword candidates and search markets, returning ranked, actionable targets to improve organic visibility.

Instructions

Find prioritized SEO opportunities for a domain or URL. 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": {
      "target": "<target>"
    },
    "name": "agentseo_opportunities_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
syncNoRequest 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.
targetYesTarget domain, subdomain or absolute page URL to analyze; use a hostname or URL, not a business name. Type: String. Required.
languageNoSupported search language code, for example en for English. Type: String. Default: "en".en
locationNoSupported geographic search-market name, for example United States; this is not a coordinate pair. Type: String. Default: "United States".United States
keyword_limitNoMaximum number of keyword candidates to inspect for opportunities. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 25.
opportunity_limitNoMaximum number of prioritized opportunities to return. Type: Safe integer. Minimum: 1. Maximum: 25. Default: 10.
include_serp_competitorsNoInclude competitors found in sampled search results when true; this may require additional upstream analysis. Type: Boolean. Default: false.
include_competitor_discoveryNoDiscover additional competing domains when true instead of relying only on the target data. Type: Boolean. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.5
    • addedInput schema / properties / include_competitor_discovery / description
      Added value: +"Discover additional competing domains when true instead of relying only on the target data. Type: Boolean. Default: false."
    • addedInput schema / properties / include_serp_competitors / description
      Added value: +"Include competitors found in sampled search results when true; this may require additional upstream analysis. Type: Boolean. Default: false."
    • addedInput schema / properties / keyword_limit / description
      Added value: +"Maximum number of keyword candidates to inspect for opportunities. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 25."
    • 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_limit / description
      Added value: +"Maximum number of prioritized opportunities to return. Type: Safe integer. Minimum: 1. Maximum: 25. Default: 10."
    • 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: -"Domain or URL to analyze"New value: +"Target domain, subdomain or absolute page URL to analyze; use a hostname or URL, not a business name. Type: String. Required."
  2. First observedv0.1.4

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description reinforces this with a concrete consequence: credits are consumed and a repeat call can spawn new charged work. That is meaningful context an agent cannot infer from a boolean hint. It still omits expected latency/whether results are cached across calls, so it falls short of a 5.

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 tight sentences, purpose first and the cost caveat second, with no filler or repetition of schema content. Every clause earns its place.

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 an 8-parameter, credit-consuming, open-world analysis tool with no output schema, the description never characterizes what comes back (e.g., a ranked opportunity list, scoring basis) or roughly how expensive a call is. The cost/polling warning is present, but an agent sizing up the response and budget is still missing pieces.

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 all eight parameters are already fully documented in the schema, including the sync/polling caveat and target format. The description adds no parameter-level meaning beyond restating that the target is a domain or URL. Baseline 3 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?

States a specific verb and resource: "Find prioritized SEO opportunities for a domain or URL." An agent knows exactly what this produces. However, it does not distinguish itself from closely related siblings such as agentseo_opportunities_brief, agentseo_backlinks_opportunity_finder, or agentseo_content_gap, so sibling selection still requires guesswork.

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 by the verb "find" — there is no explicit statement of when to prefer this over agentseo_opportunities_brief or the other opportunity/gap tools. The one real guideline is the warning that repeating the call creates new charged work, which is a useful operational constraint but not a when-to-use rule.

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

Deploy Server

Other Tools