Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_upload_media_from_url

Upload media from a remote URL directly to WordPress. Specify alt text, title, caption, and description for the uploaded file.

Instructions

Upload media to WordPress from a remote URL

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": {
      "url": "<url>"
    },
    "name": "wp_upload_media_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
altNoAlt text for images
urlYesImage or file URL to upload
titleNo
captionNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden. It only states the basic action without disclosing side effects, permission requirements (e.g., upload_files capability), file type/ size limits, error handling, or return behavior. This is insufficient for an upload tool.

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 sentence with no unnecessary words, effectively communicating the core function.

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 the tool has 5 parameters, no output schema, and no annotations, the description is too minimal. It does not explain return values (e.g., media ID), error scenarios, or usage prerequisites, making it incomplete for reliable agent use.

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?

The input schema has 5 parameters but only 2 have descriptions (url and alt). Schema description coverage is 40%, and the tool description adds no extra meaning beyond what the schema already provides. Parameters like title, caption, and description lack any explanation.

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?

The description clearly states the verb 'upload', the resource 'media', and the source 'from a remote URL'. It is specific and distinguishes from the sibling tool wp_upload_media_from_base64.

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?

The description implies the tool is for uploading media from a remote URL, which is clear context. However, it does not explicitly mention alternatives or when not to use it, but the name and description suffice for basic guidance.

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