Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Bulk reassign media

wordpress_bulk_reassign_media
Destructive

Reassign the parent post of up to 100 WordPress media attachments in a single call, enabling moves between posts or detachment via target_post=0.

Instructions

[UNIFIED] Reassign the parent post of a list of media attachments in a single call. Useful for moving attachments between posts, or detaching (use target_post=0). Max 100 IDs. Returns processed / errors / total.

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>",
      "media_ids": "<media_ids>",
      "target_post": "<target_post>"
    },
    "name": "wordpress_bulk_reassign_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
media_idsYes
target_postYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.13.1

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already mark this as destructive and non-read-only, and the description adds useful behavioral details: bulk limit, detach semantics, and returned processed/errors/total fields. It does not explain atomicity or how partial failures are handled beyond the presence of an errors result.

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 compact and front-loaded, with the core action first and the useful constraints immediately after. Every sentence contributes practical information with no filler.

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 bulk destructive media operation with three required parameters and no output schema, the definition covers the main operational details: limit, detach behavior, and return shape. It could still clarify site scoping or partial-failure semantics, but it is largely complete.

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 0%, so the description must carry parameter meaning. It explains target_post=0 for detaching and the 100-ID cap for media_ids, but it does not describe the site parameter or specify the expected media_ids element format.

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 states a specific verb and resource: reassigning the parent post of media attachments in bulk. It clearly distinguishes this from deleting or updating media by focusing on parent-post reassignment, and it explains the detach case via target_post=0.

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?

It gives clear usage context: moving attachments between posts or detaching them with target_post=0, and it states the 100-ID limit. It does not explicitly name alternatives such as single-item media update or bulk delete, but the intended use case is clear.

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