Skip to main content
Glama

Get file

get_file
Read-only

Fetches a file from a URL and returns it in a format suitable for FastMcP.

This tool can be used to fetch any file type, including images, PDFs, etc. The framework will handle the encoding and packaging of the file.

Scope: one URL per call, with the result returned into the conversation. For many URLs, a whole site, output written to a file or directory, resumable jobs, or a scheduled re-run, use the ScrapingBee CLI instead — scrapingbee scrape --input-file urls.txt --output-dir results, scrapingbee crawl URL --save-pattern ..., scrapingbee schedule --every. This server has no batch, crawl, file-output or scheduling equivalent.

Docs: https://www.scrapingbee.com/documentation/remote-mcp/

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the file to fetch.
deviceNodesktop (default) or mobile.desktop
cookiesNoSemicolon-separated cookies to send to the target.
timeoutNoRequest timeout in milliseconds (1000–140000, default 140000).
render_jsNoWhether to use headless-browser rendering (default False).
session_idNoInteger 0–10000000 to reuse an IP for up to 5 minutes.
country_codeNoISO 3166-1 alpha-2 country code (e.g. "fr", "us") to route the request through an IP in that country. Only takes effect when premium_proxy is True.
custom_googleNoSet to True if the url is a google domain in the following format: <subdomain>.google.<top-level-domain> (Example: translate.google.com, mail.google.com, www.google.co.in etc)
premium_proxyNoWhether to use a premium proxy for the request. Use it only if you are getting blocked by the website.

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?

readOnlyHint=true in the annotations already establishes the safety profile, and the description usefully adds that the framework handles encoding and packaging and that results land directly in the conversation rather than on disk. It still leaves open how large or binary payloads are surfaced and whether there are size limits, which matters for a file-fetching tool with nine tuning parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structure is strong: an opening statement of what it does, a scope block, an explicit exclusion list, and a docs pointer. Minor waste exists where 'This server has no batch, crawl, file-output or scheduling equivalent' restates the preceding sentence, and the CLI command examples are somewhat verbose for a tool description.

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

Completeness5/5

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

For a read-only nine-parameter fetch tool with a fully documented schema and no output schema, the description covers purpose, scope, result destination, and out-of-scope workloads, which is everything an agent needs to decide whether to call it. The phrase 'a format suitable for FastMcP' is vague about the return payload, but with no output schema this is a minor residual gap rather than a blocking omission.

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 description coverage is 100%, so every one of the nine parameters is already documented in the input schema, including defaults, ranges, and proxy/rendering caveats. The description adds only the 'one URL per call' constraint and no additional parameter semantics, so baseline 3 applies.

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 ('Fetches a file from a URL') and clarifies that any file type, including images and PDFs, is supported, which implicitly separates it from text/HTML-oriented siblings like get_page_text and get_page_html. It does not explicitly name those siblings, so the differentiation is inferential 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?

Scope is stated positively (one URL per call, result returned into the conversation) and negatively with concrete alternatives for batch, crawl, file output, resumable jobs, and scheduling, going so far as to give CLI command examples. The gap is that the alternatives offered are all CLI-based; it never says when to prefer get_file over the in-server siblings such as get_page_html or get_screenshot.

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.

Resources