Skip to main content
Glama

get_resource_download_formats

Download Freepik resources in specific formats by providing resource ID and desired format like PSD, AI, or SVG for precise file retrieval.

Instructions

Retrieve a resource by specifying both the resource ID and the format. This endpoint allows for precise downloading of resources in the desired format.

Path Parameters:

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

  • resource-format (Required): Resource format

Responses:

  • 200 (Success): OK

    • 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"
    },
    {
      "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"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resource-idYesPhoto, video or PSD resource ID
resource-formatYesResource format
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions the tool retrieves/downloads resources and includes HTTP response codes (e.g., 200, 400, 429), it lacks critical behavioral details: it doesn't specify authentication requirements, rate limits beyond the 429 error mention, whether it's read-only or mutative, what happens on success (e.g., returns signed URLs), or any side effects. The description is insufficient for a tool with no annotation coverage.

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 poorly structured and verbose. It starts with a clear purpose statement but then includes extensive, redundant HTTP response documentation (e.g., multiple error codes with examples) that belongs in an output schema or annotations, not in the description. This bloats the text without adding helpful guidance for tool selection, making it inefficient and not front-loaded.

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

Completeness2/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 is incomplete for a tool with 2 parameters. It lacks essential context: no explanation of return values (though the 200 response example shows data with URLs, this isn't clarified in the description text), no behavioral traits like auth needs or rate limits, and no differentiation from siblings. The HTTP error details don't compensate for these gaps, making it inadequate for informed tool use.

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 fully documents both parameters ('resource-id' and 'resource-format') with descriptions and enum values. The description adds minimal value beyond the schema, only restating that parameters are required for precise downloading. No additional syntax, format details, or examples are provided in the description text itself.

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: 'Retrieve a resource by specifying both the resource ID and the format' and 'allows for precise downloading of resources in the desired format.' It specifies the verb (retrieve/download) and resource (resource by ID and format). However, it doesn't explicitly differentiate from sibling tools like 'download_resource_by_id' or 'get_resource_detail_by_id', which appear to serve similar purposes with different approaches.

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 sibling tools like 'download_resource_by_id' or 'get_resource_detail_by_id', nor does it specify prerequisites, constraints, or typical use cases. The only implied usage is for downloading resources with specific formats, but no comparative context is given.

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