Skip to main content
Glama

compress_remote_image

Reduce the size of a remote image by providing its URL, specify the output format, and save it to an absolute path for efficient storage and faster loading.

Instructions

Compress a remote image file by giving the URL of the image

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageUrlYesThe URL of the image file to compress
outputFormatNoThe format to save the compressed image file
outputPathNoThe ABSOLUTE path to save the compressed image file

Implementation Reference

  • The MCP tool handler function that processes the incoming request for compress_remote_image, extracts parameters, calls the core handler, and formats the response.
    compress_remote_image: async (request) => {
      const result = await handleCompressRemoteImageTool(
        request.params.arguments as {
          imageUrl: string;
          outputPath?: string;
          outputFormat?: SupportedImageTypes;
        },
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
        metadata: {},
      };
    },
  • Tool definition including the name, description, and input schema for validating parameters like imageUrl, outputPath, and outputFormat.
    const COMPRESS_REMOTE_IMAGE_TOOL: Tool = {
      name: 'compress_remote_image',
      description: 'Compress a remote image file by giving the URL of the image',
      inputSchema: {
        type: 'object',
        properties: {
          imageUrl: {
            type: 'string',
            description: 'The URL of the image file to compress',
            example: 'https://example.com/image.jpg',
          },
          outputPath: {
            type: 'string',
            description: 'The ABSOLUTE path to save the compressed image file',
            example: '/Users/user/Downloads/image_compressed.jpg',
          },
          outputFormat: {
            type: 'string',
            description: 'The format to save the compressed image file',
            enum: SUPPORTED_IMAGE_TYPES,
            example: 'image/jpeg',
          },
        },
        required: ['imageUrl'],
      },
    };
  • Core helper function that performs the actual compression of the remote image using tinify.fromUrl, handles output format conversion, determines output path, saves the file, and computes compression statistics.
    async function handleCompressRemoteImageTool({
      imageUrl,
      outputPath,
      outputFormat,
    }: {
      imageUrl: string;
      outputPath?: string;
      outputFormat?: SupportedImageTypes;
    }) {
      tinify.key = config.apiKey!;
      const source = tinify.fromUrl(imageUrl);
      let ext = path.extname(imageUrl).slice(1);
    
      if (outputFormat) {
        source.convert({
          type: outputFormat,
        });
        ext = outputFormat.split('/')[1];
      }
    
      let dest = outputPath;
      if (!dest) {
        const dir = path.dirname(imageUrl);
        const basename = path.basename(imageUrl, path.extname(imageUrl));
        dest = path.join(dir, `${basename}.${ext}`);
      }
    
      await source.toFile(dest);
    
      const originalSize = (await fetch(imageUrl).then((res) => res.arrayBuffer())).byteLength;
      const compressedSize = fs.statSync(dest).size;
      const compressionRatio = (originalSize - compressedSize) / originalSize;
    
      return {
        originalSize,
        compressedSize,
        compressionRatio,
      };
    }
  • src/tools.ts:117-117 (registration)
    Exports the array of Tool objects including COMPRESS_REMOTE_IMAGE_TOOL for registration with the MCP server.
    export const TOOLS = [COMPRESS_LOCAL_IMAGE_TOOL, COMPRESS_REMOTE_IMAGE_TOOL, RESIZE_IMAGE_TOOL];
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions compression but doesn't disclose quality loss, file size reduction expectations, network timeout behavior, authentication needs for remote URLs, or error handling. This is inadequate for a tool that processes external resources.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for the tool's complexity.

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?

For a tool that fetches and processes remote images with 3 parameters and no annotations or output schema, the description is insufficient. It lacks critical context about compression behavior, error scenarios, output expectations, and sibling tool differentiation, leaving significant gaps for an AI agent.

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 all parameters. The description adds no additional meaning beyond implying 'imageUrl' is required, which is already clear from the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('compress') and resource ('remote image file'), specifying it works on images accessible via URL. It distinguishes from 'compress_local_image' by specifying 'remote' but doesn't explicitly differentiate from 'resize_image' beyond the core action.

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?

No guidance is provided on when to use this tool versus alternatives like 'compress_local_image' or 'resize_image'. The description only states what it does, not when it's appropriate or what prerequisites exist for remote image access.

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

Related 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/zhendi/tinypng-mcp-server'

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