Skip to main content
Glama
Sign In
wordpress-mcp

wordpress-mcp

by cvrt-jh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

seo_import_csv

Import post SEO metadata from CSV into WordPress to update SEO titles, descriptions, and meta fields for existing posts.

Instructions

Import post SEO meta from CSV.

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>"
    },
    "name": "seo_import_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesCSV import payload
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.4.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it discloses nothing about what an import does to existing meta (merge vs overwrite), the expected CSV structure, or whether it requires elevated capability. Only the bare operation is named, so this is a significant gap for a mutating import tool.

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 efficient sentence with the action front-loaded and no filler. It is arguably too terse for an import tool, but nothing in it is wasted.

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?

For an import tool with no annotations, no output schema, and an unspecified nested data payload, the description leaves critical information missing: CSV format/columns, overwrite semantics, and error behavior. It is not adequate for correct invocation.

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 100%, so both site and data are documented in the schema, giving a baseline of 3. However, the description adds nothing about the opaque data payload (nested object with additionalProperties) or its expected CSV columns, leaving the one parameter that needs explanation unexplained.

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?

States a specific verb (import), resource (post SEO meta) and source format (CSV), which distinguishes it from seo_import_settings, seo_import_redirects and seo_import_migrate. It does not explicitly name those siblings, so it falls short of a 5.

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, no mention of prerequisites, and no routing to the CSV export or the other import tools. Nothing tells an agent when this is preferable to seo_bulk_update_posts_seo or seo_import_migrate.

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