Skip to main content
Glama
Sign In
AgentSEO MCP Server

AgentSEO MCP Server

by AgentSEO-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

AgentSEO Extract

agentseo_extract
Destructive

Extract content from a URL and convert it to Markdown for SEO analysis, with optional image details included.

Instructions

Extract content from a URL and convert to Markdown. 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>"
    },
    "name": "agentseo_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute web page URL to analyze; use an http:// or https:// URL. Type: String. Format: absolute URL. Required.
include_imagesNoInclude extracted image information with the returned page content when true. Type: Boolean. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.5
    • addedInput schema / properties / include_images / description
      Added value: +"Include extracted image information with the returned page content when true. Type: Boolean. Default: false."
    • changedInput schema / properties / url / description
      Previous value: -"The URL to scrape"New value: +"Absolute web page URL to analyze; use an http:// or https:// URL. Type: String. Format: absolute URL. Required."
  2. First observedv0.1.4

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=true, so the risk profile is largely covered. The description adds genuinely new context beyond them: the call consumes AgentSEO credits and repeating it can create new charged work, which reinforces the non-idempotent hint. It does not say what 'destructive' means here or what happens on a failed/partial extraction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the operation stated first and the cost caveat second. No filler, though the credit sentence could be slightly more specific about what triggers the extra charge.

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?

With no output schema, the description usefully names the return format (Markdown), and the annotations carry the safety profile. For a 2-param, credit-consuming, open-world extraction tool it still omits failure behavior, size/latency expectations, and any hint about which sibling to prefer.

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 coverage is 100%, so url and include_images are fully documented in the schema, including format and default. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

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: 'Extract content from a URL and convert to Markdown.' The conversion output is named, so an agent knows what it gets back. It does not differentiate from nearby tools such as agentseo_ai_overview_extract or agentseo_search, which also take a URL/page target.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no named alternative among the ~45 sibling tools that also operate on a URL. The credit warning is a cost caution, not routing guidance, so the agent must infer selection from the name alone.

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