Skip to main content
Glama

Add content sources during setup

flypost_add_onboarding_sources

Import the user's existing content into Flypost, so posts are grounded in what they have written or recorded. Leave everything empty to skip.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flypost_add_onboarding_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoOther single pages to import.
blog_urlsNoBlog or news sections of their site.
project_idNoProject (workspace) id. Omit to use the active project, or the only project if there is just one.
youtube_urlNoTheir YouTube channel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already flag this as a non-read-only, open-world, non-destructive write, so the safety profile is covered. The description adds the grounding purpose and the skip behavior but says nothing about what actually happens to the supplied URLs (fetching/scraping, latency, failure modes), which is important given openWorldHint=true means external network ingestion.

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, purpose front-loaded, with the opt-out rule cleanly appended. Nothing is redundant or padded.

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?

For a four-parameter, all-optional ingestion tool with full schema coverage and clear annotations, the description covers intent and the empty-case behavior. It stops short of saying how this fits into the onboarding sequence or what happens to the ingested content afterwards, which an agent coordinating with flypost_start_onboarding / flypost_finish_onboarding would benefit from.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline would be 3; the description nudges higher by making explicit that every parameter is optional and the call can legitimately be sent with no content at all. It adds no semantics about the caps (10 URLs, 12 blog URLs) or the difference between urls and blog_urls beyond what the schema already says.

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 ('Import the user's existing content') plus the downstream purpose ('posts are grounded in what they have written or recorded'), so the intent is unambiguous. It never mentions the onboarding framing implied by the tool name, and it does not distinguish itself from the individual ingestion siblings (flypost_add_source_url, flypost_add_source_document, flypost_add_source_text, flypost_add_onboarding_linkedin), which is the one clear gap.

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?

'Leave everything empty to skip' is a genuine usage rule that tells the agent the tool is optional during a flow. However, there is no guidance on when to prefer this bulk import over the per-item siblings, nor any prerequisite or sequencing information despite 'onboarding' being in the name.

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.