Skip to main content
Glama
Sign In
Apex Flow 3D Scraper

Apex Flow 3D Scraper

Official
by Apexflowlabsllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

map_site

Discover up to 1,000 public sitemap URLs from a site, with optional search filtering, to plan scraping and content extraction. A nonempty result costs one credit.

Instructions

Discover up to 1,000 public sitemap URLs. A nonempty map costs one credit.

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": "map_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
limitNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description still conveys two useful behavioral facts: the result cap and that a nonempty result costs one credit. It omits whether the call is read-only in practice, whether it crawls the site or only reads the sitemap, how long it takes, and why a failed/empty map is free.

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 with no filler; the capability cap is front-loaded and the billing note follows immediately. Nothing is redundant or buried.

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 3-parameter tool with no annotations, no output schema, and zero schema coverage, the description is too thin. It should explain what a "map" returns, what `search` filters, and the limit ceiling, since no structured field covers these.

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?

Schema description coverage is 0%, so the burden is fully on the description, yet it never explains the three parameters. "Up to 1,000" only loosely hints at the limit parameter (which defaults to 100), and the `search` filter and `url` input format are entirely unexplained.

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?

"Discover up to 1,000 public sitemap URLs" gives a specific verb (discover) and resource (public sitemap URLs), plus a scope cap. It does not differentiate itself from siblings like scrape_page or scrape_batch, which also retrieve web content, so an agent must infer the distinction.

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?

The description contains no when-to-use guidance, no prerequisites (e.g., site must have a sitemap), and no mention of alternatives. "Public" hints at a domain constraint but does not tell the agent when this beats scraping.

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