Skip to main content
Glama

Import a file from a URL

import_file_from_url

Fetch a PDF, Office file, image or EPUB from a public link into FynePDF and get its file_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": {
      "url": "<url>"
    },
    "name": "import_file_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
file_nameNo

Output Schema

NameRequiredDescriptionDefault
kindYes
bytesYes
pagesYes
file_idYes
filenameYes
expires_atYes
download_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedOutput schema / properties / bytes / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / bytes / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / download_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / download_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / pages / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / pages / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already disclose the important traits: readOnlyHint=false, openWorldHint=true (network egress), idempotentHint=false and destructiveHint=false. The description adds useful context beyond that by listing accepted content types and confirming the tool returns a file_id, but says nothing about network failure modes, size limits, or which import job/response shape results when the fetch is slow or fails.

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?

A single sentence that front-loads the formats, the source constraint, the destination, and the returned identifier. Nothing is redundant and nothing padding-like is present.

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?

Return values are covered by the existing output schema and safety traits by annotations, so the description only needs to cover inputs and operational constraints. It is adequate on the URL source requirement but leaves the optional file_name behavior, size/type limits, and failure handling undescribed for a tool that reaches the open internet.

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 description carries the full burden for two parameters and largely fails it. 'Public link' is a meaningful constraint on url (no auth-protected or local paths), but file_name is never mentioned at all — no statement of default naming, length limit (maxLength 200), or behavior when omitted or when a file with that name exists.

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 names a specific action and resource ('Fetch a PDF, Office file, image or EPUB from a public link into FynePDF') and states the concrete result ('get its file_id'). It implicitly separates itself from the sibling upload_file by requiring a public link rather than a local upload, though it never names that sibling explicitly.

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?

Usage is only implied: the agent can infer this is the tool for pulling remote content by URL rather than uploading local bytes or listing existing files. There is no explicit when-to-use/when-not statement, no guidance about non-public or authenticated URLs, and no pointer to the alternative sibling (upload_file) for local files.

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.