Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

whatsapp_get_media

Read-onlyIdempotent

Retrieve the download URL and metadata for a WhatsApp media object using its media ID, enabling direct access to shared media files.

Instructions

Get the download URL and metadata for a WhatsApp media object by 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": {
      "bearer_token": "<bearer_token>",
      "media_id": "<media_id>"
    },
    "name": "whatsapp_get_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_idYes
bearer_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds the useful behavioral fact that the return is a URL plus metadata, but omits operationally critical traits such as the fact that WhatsApp media URLs are short-lived, or that the returned URL must itself be fetched.

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?

A single front-loaded sentence with no filler; the essential information appears first. It is arguably too terse rather than padded, so the efficiency itself is not penalized.

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?

For a two-parameter read tool with a full annotation profile and no output schema, this is close to adequate. What is missing is meaningful for an agent: what bearer_token is and where it comes from, and how long the returned download URL stays valid.

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 coverage is 0%, so the description must carry parameter meaning and it only does half the job: 'by ID' implies media_id identifies the media object, but bearer_token is left entirely unexplained (required auth credential, which account/scope). The gap matters because a missing or wrong token would look like a bad media ID.

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?

Names a specific verb ('Get') and a precise resource ('download URL and metadata for a WhatsApp media object'), so an agent knows exactly what it returns. It does not explicitly differentiate itself from the sibling whatsapp_upload_media, which is the inverse operation and the natural confused alternative.

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?

There is no when-to-use guidance and no mention of the sibling pair sequence (upload media to obtain an ID, then get media by that ID). Nothing says whether this is the correct tool when the agent already has a media ID versus when it must first call whatsapp_upload_media.

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

Deploy Server

Other Tools