Skip to main content
Glama

Add source URL

flypost_add_source_url

Ingest one URL (blog post, YouTube video, or generic link) into a Brain notebook. Blocks until the item is scraped and embedded (typically under 2 minutes).

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>",
      "source_package_id": "<source_package_id>"
    },
    "name": "flypost_add_source_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
titleNo
item_typeNo
is_own_contentNoTrue when the user wrote this content themselves (affects drafting attribution).
source_package_idYesNotebook/source package id from flypost_list_sources.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, so safety is partly covered. The description adds a genuinely valuable trait the annotations cannot convey: the call is synchronous and blocks until scraping and embedding finish, with a typical duration under 2 minutes. It still omits failure behavior for unfetchable URLs and duplicate-URL handling.

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, no filler, and the blocking/duration caveat is placed immediately after the purpose so an agent sees the cost of the call up front. Nothing repeats the tool name or title.

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 a 5-parameter ingestion tool with no output schema, the description covers the essential operational facts: accepted input kinds and the synchronous, multi-minute execution model. What is missing is what the call yields on success and how duplicates or fetch failures surface, which matters more given the absence of an output schema.

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 40%, so the description must compensate somewhat. It does so by spelling out the real-world meaning of the item_type values (blog post, YouTube video, generic link), which maps directly to the only enum parameter. It says nothing about title, source_package_id, or is_own_content, leaving over half the parameters to the schema.

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?

"Ingest one URL (blog post, YouTube video, or generic link) into a Brain notebook" gives a specific verb (ingest), a specific resource (a single URL), and the accepted content shapes. It implicitly separates itself from the document/text siblings by restricting input to a URL, but never names those siblings, so the differentiation must be inferred.

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 parenthetical list of accepted URL kinds implies when this tool is appropriate, and the blocking note implies when it is not (i.e., don't use it for fast fire-and-forget adds). However, there is no explicit when-to-use statement and no routing to flypost_add_source_document or flypost_add_source_text for non-URL content.

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.