Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Upload media from base64

wordpress_upload_media_from_base64
Destructive

Upload a base64-encoded file directly to the WordPress media library, making it useful for adding chat-attached images or files under about 10 MB.

Instructions

[UNIFIED] Upload a base64-encoded file directly to the WordPress media library. For chat-attached images/files smaller than ~10 MB. Use upload_media_from_url for larger files or chunked path later.

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": {
      "site": "<site>",
      "data": "<data>",
      "filename": "<filename>"
    },
    "name": "wordpress_upload_media_from_base64"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
mimeNo
siteYes
titleNo
captionNo
alt_textNo
filenameYes
convert_toNo
set_featuredNo
skip_optimizeNo
attach_to_postNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.13.1

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already flag this as a non-idempotent, destructive write, but the description adds nothing about what gets created or modified, permission requirements, or the side effects of the non-obvious flags (set_featured, attach_to_post, convert_to, skip_optimize). For an 11-parameter mutation tool it repeats only what the annotations already say implicitly.

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?

Three short sentences with the core action and size constraint front-loaded; no filler. The '[UNIFIED]' prefix and the dangling 'chunked path later' are minor noise but don't obstruct reading.

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?

With 11 undocumented parameters, no output schema, and a destructive write hint, the definition should explain at least the high-impact options and what the tool returns or attaches. It covers only size/format routing, leaving an agent unable to use most of the schema safely.

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 description coverage is 0% across 11 parameters, so the description must carry the meaning, yet it only implies what 'data' is and never mentions filename, site, mime conversion, featured-image assignment, or post attachment. The meaning of the parameters that most change tool behavior is left entirely undocumented.

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 base64-encoded file directly to the WordPress media library') and immediately distinguishes the input form (base64) from the sibling wordpress_upload_media_from_url. An agent can pick this tool without opening the schema.

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 a concrete selection rule: chat-attached images/files under ~10 MB, otherwise use upload_media_from_url, and mentions a chunked path for still larger payloads. The trailing 'or chunked path later' is vague and doesn't name which chunked sibling to start with, which keeps it below a 5.

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