Skip to main content
Glama

download_resource_by_id

Download specific Freepik resources like vectors, PSDs, photos, and AI content by providing the resource ID, with optional image size adjustment for photos.

Instructions

Download a specific resource by providing the resource ID. This endpoint supports downloading various types of resources including vectors, PSDs, photos, and AI-generated content.

Path Parameters:

  • resource-id (Required): Photo, video or PSD resource ID

Query Parameters:

  • image_size: Resizes the photo to a specified size while maintaining aspect ratio. Accepts a pixel value (100px to 2000px) or keywords small(1000px), medium(1500px), large(2000px), original corresponding to standard website sizes. The size depends on the image orientation, the longest side of the image will be resized to the specified size. If not specified, the highest resolution is provided. Applicable only to photos.

Responses:

  • 200 (Success): OK Response

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "data": {
    "signed_url": "https://img.freepik.com/premium-photo/close-up-cat-resting_1048944-9269194.jpg?t=st=1725276607~exp=1725280207~hmac=1538f1b294fc3a19a19e9f02ceeb6594a9a1e36a900de85d47bbd386e27dddbe",
    "filename": "blackboard-template.zip",
    "url": "https://downloadscdn5.freepik.com/d/1137445/blackboard-template.zip"
  }
}
  • 400: Bad Request - The server could not understand the request due to invalid syntax.

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "message": "message"
}
  • 401: Unauthorized - The client must authenticate itself to get the requested response.

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "message": "message"
}
  • 403: Forbidden - The client does not have permission to access the requested resource.

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "message": "message"
}
  • 404: Not Found - The server can not find the requested resource.

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "message": "message"
}
  • 429: Too Many Requests - The client has sent too many requests in a given amount of time.

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "message": "message"
}
  • 500: Internal Server Error - The server has encountered a situation it doesn't know how to handle.

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "message": "Internal Server Error"
}
  • 503: Service Unavailable

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "message": "Service Unavailable. Please try again later."
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resource-idYesPhoto, video or PSD resource ID
Accept-LanguageNoSpecifies the search query language using the ISO 639-1 (2-letter language code) and the ISO 3166-1 (2-letter country code) for language variants. The API will use "en-US" as a default language for processing if a code is not provided, or does not exist.
image_sizeNoResizes the photo to a specified size while maintaining aspect ratio. Accepts a pixel value (100px to 2000px) or keywords small(1000px), medium(1500px), large(2000px), original corresponding to standard website sizes. The size depends on the image orientation, the longest side of the image will be resized to the specified size. If not specified, the highest resolution is provided. Applicable only to photos.
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the resource types supported (vectors, PSDs, photos, AI-generated content) and includes HTTP response codes with examples, which adds behavioral context like authentication needs (401), rate limits (429), and error handling. However, it lacks details on permissions, side effects, or performance characteristics, leaving gaps for a mutation-like download operation.

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

Conciseness2/5

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

The description is overly verbose and poorly structured. It includes extensive HTTP response details that belong in an output schema or annotations, not in the description. The first two sentences are front-loaded, but the bulk is redundant parameter info and response examples, making it inefficient and cluttered.

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?

Given no annotations and no output schema, the description compensates by including response codes and examples, which helps understand behavior. However, for a download tool with 3 parameters and mutation-like effects, it should better explain side effects, return values, and usage context. It's minimally adequate but has clear gaps in completeness.

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 the schema already documents all parameters thoroughly. The description repeats parameter details in the 'Path Parameters' and 'Query Parameters' sections, adding no new semantic meaning beyond what's in the schema. This meets the baseline of 3, as the schema does the heavy lifting without extra value from the description.

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 clearly states the tool's purpose: 'Download a specific resource by providing the resource ID' with a verb ('download') and resource ('resource'). It distinguishes from siblings like 'get_resource_detail_by_id' (which retrieves metadata) and 'download_icon_by_id' (which is icon-specific). However, it doesn't explicitly contrast with all siblings, keeping it at 4 rather than 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention siblings like 'get_resource_download_formats' (which might list formats before download) or 'download_icon_by_id' (for icons specifically). There's no context about prerequisites or when-not-to-use scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/freepik-company/freepik-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server