Skip to main content
Glama
Sign In
AgentSEO MCP Server

AgentSEO MCP Server

by AgentSEO-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

AgentSEO Competitor Content Gap Matrix

agentseo_content_competitor_gap_matrix
Destructive

Compare supplied own and competitor pages to surface missing topics, weak coverage, format gaps, and buyer-stage gaps, then prioritize content opportunities.

Instructions

Compare supplied own and competitor pages to find missing topics, weak coverage, format gaps, and buyer-stage gaps. 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": {
      "competitors": "<competitors>"
    },
    "name": "agentseo_content_competitor_gap_matrix"
  }
}

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.
targetNoYour target brand, domain or URL used to scope this workflow; supply the entity you want assessed. Type: String. Optional; no client default.
own_pagesNoYour supplied page records for comparison with competitor pages; an empty list represents no supplied owned coverage. Type: Array. Maximum: 100 items. Default: [].
competitorsYesCompetitor domains with their supplied page records; no competitor crawl is performed. Type: Array. Minimum: 1 items. Maximum: 10 items. Required.
focus_topicsNoTopics to prioritize in the supplied competitor content comparison. Type: Array. Maximum: 100 items. Default: [].
max_opportunitiesNoMaximum number of prioritized opportunities to return from the supplied comparison. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed38 schema fields changedv0.1.5
    • addedInput schema / properties / competitors / description
      Added value: +"Competitor domains with their supplied page records; no competitor crawl is performed. Type: Array. Minimum: 1 items. Maximum: 10 items. Required."
    • addedInput schema / properties / competitors / items / description
      Added value: +"One competitor domain with its supplied page records. Type: Object. Required."
    • addedInput schema / properties / competitors / items / properties / domain / description
      Added value: +"Website hostname associated with this record, for example example.com rather than a business name. Type: String. Minimum: 1 characters. Maximum: 160 characters. Required."
    • addedInput schema / properties / competitors / items / properties / pages / description
      Added value: +"Supplied page records to compare; URLs identify the records and are not instructions to publish changes. Type: Array. Minimum: 1 items. Maximum: 100 items. Required."
    • addedInput schema / properties / competitors / items / properties / pages / items / description
      Added value: +"One supplied page record used in this comparison. Type: Object. Required."
    • addedInput schema / properties / competitors / items / properties / pages / items / properties / avg_position / description
      Added value: +"Supplied mean organic search position, where 1 is best; not an authority score. Type: Number. Minimum: 1. Maximum: 100. Optional; no client default."
    • addedInput schema / properties / competitors / items / properties / pages / items / properties / backlinks / description
      Added value: +"Count of backlinks reported for this supplied page. Type: Number. Minimum: 0. Optional; no client default."
    • addedInput schema / properties / competitors / items / properties / pages / 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 / competitors / items / properties / pages / items / properties / description / description
      Added value: +"Short summary of this supplied page; this is input evidence, not a request to generate a meta description. Type: String. Maximum: 500 characters. Optional; no client default."
    • addedInput schema / properties / competitors / items / properties / pages / items / properties / estimated_traffic / description
      Added value: +"Estimated search visits for this supplied page; use a consistent time window across compared pages. Type: Number. Minimum: 0. Optional; no client default."
    • addedInput schema / properties / competitors / items / properties / pages / items / properties / keywords / description
      Added value: +"Search phrases to evaluate or associate with the supplied page. Type: Array. Maximum: 100 items. Default: []."
    • addedInput schema / properties / competitors / items / properties / pages / items / properties / keywords / items / description
      Added value: +"One search keyword or phrase, not a comma-separated list. Type: String. Minimum: 1 characters. Maximum: 120 characters. Required."
    • addedInput schema / properties / competitors / items / properties / pages / items / properties / page_type / description
      Added value: +"Page format or classification for this record; select one of the accepted values. Type: String. Accepted values: \"unknown\", \"homepage\", \"blog_post\", \"landing_page\", \"product\", \"software\", \"local_business\", \"comparison_page\", \"guide\", \"docs\", \"template\", \"tool\", \"case_study\". Default: \"unknown\"."
    • addedInput schema / properties / competitors / items / properties / pages / items / properties / ranking_queries / description
      Added value: +"Search queries known to rank for this page from your supplied evidence. Type: Array. Maximum: 100 items. Default: []."
    • addedInput schema / properties / competitors / items / properties / pages / items / properties / ranking_queries / items / description
      Added value: +"One search query known to rank for this page. Type: String. Minimum: 1 characters. Maximum: 120 characters. Required."
    • addedInput schema / properties / competitors / items / properties / pages / items / properties / search_volume / description
      Added value: +"Estimated monthly searches for this supplied keyword or topic, not a measured page-visit count. Type: Number. Minimum: 0. Optional; no client default."
    • addedInput schema / properties / competitors / items / properties / pages / 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 / competitors / items / properties / pages / items / properties / url / description
      Added value: +"Absolute URL identifying this supplied own or competitor page; all comparison evidence comes from the supplied record. Type: String. Format: absolute URL. Required."
    • addedInput schema / properties / focus_topics / description
      Added value: +"Topics to prioritize in the supplied competitor content comparison. Type: Array. Maximum: 100 items. Default: []."
    • addedInput schema / properties / focus_topics / items / description
      Added value: +"One topic to prioritize in the competitor comparison. Type: String. Minimum: 1 characters. Maximum: 120 characters. Required."
    • addedInput schema / properties / max_opportunities / description
      Added value: +"Maximum number of prioritized opportunities to return from the supplied comparison. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 30."
    • addedInput schema / properties / own_pages / description
      Added value: +"Your supplied page records for comparison with competitor pages; an empty list represents no supplied owned coverage. Type: Array. Maximum: 100 items. Default: []."
    • addedInput schema / properties / own_pages / items / description
      Added value: +"One of your supplied pages, with coverage evidence for comparison. Type: Object. Required."
    • addedInput schema / properties / own_pages / items / properties / avg_position / description
      Added value: +"Supplied mean organic search position, where 1 is best; not an authority score. Type: Number. Minimum: 1. Maximum: 100. Optional; no client default."
    • addedInput schema / properties / own_pages / items / properties / backlinks / description
      Added value: +"Count of backlinks reported for this supplied page. Type: Number. Minimum: 0. Optional; no client default."
    • addedInput schema / properties / own_pages / 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 / own_pages / items / properties / description / description
      Added value: +"Short summary of this supplied page; this is input evidence, not a request to generate a meta description. Type: String. Maximum: 500 characters. Optional; no client default."
    • addedInput schema / properties / own_pages / items / properties / estimated_traffic / description
      Added value: +"Estimated search visits for this supplied page; use a consistent time window across compared pages. Type: Number. Minimum: 0. Optional; no client default."
    • addedInput schema / properties / own_pages / items / properties / keywords / description
      Added value: +"Search phrases to evaluate or associate with the supplied page. Type: Array. Maximum: 100 items. Default: []."
    • addedInput schema / properties / own_pages / items / properties / keywords / items / description
      Added value: +"One search keyword or phrase, not a comma-separated list. Type: String. Minimum: 1 characters. Maximum: 120 characters. Required."
    • addedInput schema / properties / own_pages / items / properties / page_type / description
      Added value: +"Page format or classification for this record; select one of the accepted values. Type: String. Accepted values: \"unknown\", \"homepage\", \"blog_post\", \"landing_page\", \"product\", \"software\", \"local_business\", \"comparison_page\", \"guide\", \"docs\", \"template\", \"tool\", \"case_study\". Default: \"unknown\"."
    • addedInput schema / properties / own_pages / items / properties / ranking_queries / description
      Added value: +"Search queries known to rank for this page from your supplied evidence. Type: Array. Maximum: 100 items. Default: []."
    • addedInput schema / properties / own_pages / items / properties / ranking_queries / items / description
      Added value: +"One search query known to rank for this page. Type: String. Minimum: 1 characters. Maximum: 120 characters. Required."
    • addedInput schema / properties / own_pages / items / properties / search_volume / description
      Added value: +"Estimated monthly searches for this supplied keyword or topic, not a measured page-visit count. Type: Number. Minimum: 0. Optional; no client default."
    • addedInput schema / properties / own_pages / 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 / own_pages / items / properties / url / description
      Added value: +"Absolute URL identifying this supplied own or competitor page; all comparison evidence comes from the supplied record. Type: String. Format: absolute URL. Required."
    • 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."
  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, idempotentHint=false, readOnlyHint=false, so the safety profile is known. The description adds cost behavior beyond that: it consumes AgentSEO credits and repeating the call creates new charged work, which is exactly the non-idempotent consequence an agent needs before retrying. It does not describe the returned opportunity format, but the charging caveat is a real value-add.

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, front-loaded with the comparison scope and followed by the cost warning. No redundant restatement of the title and nothing wasted.

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 tool with a deeply nested page/competitor schema and no output schema, the description is thin on what comes back — a ranked opportunity list capped by max_opportunities is never stated, nor is the basis for prioritization. The input side is fully covered by the schema, so this is adequate but leaves a meaningful gap on output expectations.

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 nested field is documented in-schema, so a baseline of 3 applies. The description adds only the framing that comparison evidence is supplied rather than crawled, which is already conveyed by the competitors parameter description ("no competitor crawl is performed").

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 ("Compare supplied own and competitor pages") plus the four gap classes it produces: missing topics, weak coverage, format gaps, buyer-stage gaps. The word "supplied" implicitly separates it from crawling competitors, though the sibling agentseo_content_gap is never named, so the boundary between the two is left to the agent's inference.

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 description implies usage (compare supplied page sets to surface gaps) and adds a caution about repeat calls, but gives no explicit when-to-use/when-not or routing versus agentseo_content_gap or agentseo_opportunities_find. Usage must be inferred from the tool name and parameter shapes.

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