Skip to main content
Glama

AgentSEO Extract

agentseo_extract
Destructive

Extract content from a URL and convert to Markdown.

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
urlYesThe URL to scrape
include_imagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior1/5

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

The description frames the operation as a passive read ("extract content"), while the annotations declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false. Nothing in the description explains what those destructive side effects are or how scraping behavior differs from a pure read, leaving the agent with a direct conflict between narrative and metadata.

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?

A single tight sentence with no filler, and the core action is front-loaded. Conciseness is not the problem here; under-specification is.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, an undocumented boolean parameter, and annotations that imply significant side effects, one sentence is insufficient. The agent knows neither the return shape nor the behavioral risk it is accepting by calling this.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema description coverage, the description must compensate for the undocumented parameter, but it never mentions include_images (default false) or what including images means for the Markdown output. The URL parameter is self-explanatory and already documented in the schema, so the description adds essentially nothing.

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 gives a specific verb and resource ("Extract content from a URL") plus an output transformation ("convert to Markdown"), which is far more informative than the title alone. It does not, however, distinguish this from the close sibling agentseo_ai_overview_extract, which also extracts from a URL.

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 guidance on when to use this tool versus the ~44 sibling tools, and in particular no guidance separating it from agentseo_ai_overview_extract. The agent is left to infer applicability from the one-line purpose.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.