Skip to main content
Glama
1msg MCP

1msg MCP

Official
by 1msg

create_upload_media

Upload a file or URL to WhatsApp media storage and return a numeric mediaId for use with send_file or send_sticker.

Instructions

Upload a file to WhatsApp media storage and get a numeric mediaId for later use with send_file / send_sticker (mediaId field, not body).

Pass the file as body or url — an HTTP(S) URL or a base64 data URI. The mediaId in the response is a numeric string (keep it as a string).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_upload_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
bodyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.10
    • addedInput schema / properties / body
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / payload
      Removed value: -{
      -  "additionalProperties": {},
      -  "propertyNames": {
      -    "type": "string"
      -  },
      -  "type": "object"
      -}
    • addedInput schema / properties / url
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv1.2.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses the return contract (numeric mediaId, keep as string) and that the file lands in WhatsApp media storage. It omits permission/auth requirements, file size or MIME-type limits, and whether repeat uploads are deduplicated — relevant for an upload/mutation tool with zero 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.

Conciseness4/5

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

Short and front-loaded: purpose first, then the parameter contract, then the return-value caveat, with the key warning ('not body') called out parenthetically. Slight redundancy between 'Pass the file as body or url' and the schema's own field names, but no filler sentences.

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

Completeness4/5

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

For a two-parameter upload tool with no output schema, the definition covers purpose, input forms, and the shape of the returned value, which is what an agent needs to chain into send_file/send_sticker. Missing only operational constraints (size/media-type limits, auth) that would matter at call time.

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 coverage is 0% and both parameters are bare strings, so the description does real work: it identifies url as an HTTP(S) URL or base64 data URI and body as the file payload. However it is ambiguous whether body itself accepts a data URI or raw content, and it never states that the two are mutually exclusive options, leaving a gap the schema cannot fill.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Upload a file to WhatsApp media storage') plus the concrete payoff ('get a numeric mediaId for later use with send_file / send_sticker'), which distinguishes it from siblings like retrieve_media, delete_media, and the send_* family.

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?

Gives clear context for when to reach for it — whenever a mediaId is needed downstream — and even corrects the common misuse ('mediaId field, not body') when calling send_file/send_sticker. It stops short of naming alternatives such as retrieve_media for the reverse direction or stating that this is unnecessary when sending by URL directly to a send_* tool.

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