Skip to main content
Glama

Crawl source archive

flypost_archive_source

Crawl a whole blog (sitemap) or YouTube channel into a source package. Long-running: returns a job handle immediately — check progress with flypost_job_status {type:'source-ingest', id: source_package_id}.

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": {
      "source_package_id": "<source_package_id>",
      "archive_url": "<archive_url>"
    },
    "name": "flypost_archive_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
archive_urlYesThe blog root or YouTube channel URL.
source_package_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false. Beyond that, the description usefully discloses the non-obvious asynchronous contract — it returns a job handle immediately rather than results — and names the exact status-check tool and type string. It does not say what happens if a package is re-crawled, whether the operation costs quota, or what permissions the source requires.

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 with the capability front-loaded and the async caveat plus recovery path packed into the second. Nothing is wasted or repeated from the schema.

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

Completeness4/5

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

For an async job-launcher with no output schema, the description covers what the call returns (a job handle) and how to follow up, which is the critical missing piece. The gaps — meaning of source_package_id, enum semantics for kind, and re-crawl behavior — are secondary but real for a 3-parameter mutation.

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 only 33%: only archive_url is documented inline. The description partially compensates by scoping archive_url to blog root or channel URL and by tying source_package_id to the job-status call. However, the kind enum values ('auto', 'page') are never explained, and it is ambiguous whether source_package_id is caller-generated or produced by the crawl.

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?

"Crawl a whole blog (sitemap) or YouTube channel into a source package" gives a specific verb (crawl) and resource (blog/channel), and the word "whole" signals bulk ingestion versus the single-document siblings like flypost_add_source_url. It stops short of naming an alternative, so the differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

The description clearly frames the async usage pattern: it says the call is long-running and that progress must be checked via flypost_job_status with the specific type value 'source-ingest'. It gives no explicit when-not guidance (e.g., use add_source_url for a single page) or preconditions such as required auth or an existing package.

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.