Skip to main content
Glama

seo_bulk_update_posts_seo

Update SEO metadata for up to 100 WordPress posts in one call: titles, descriptions, robots, schema, and social tags. Null values delete fields; omitted fields stay unchanged.

Instructions

Bulk update SEO meta of up to 100 posts. Each item is { id, ...fields } with the same fields as seo_update_post_seo (null deletes a field, omitted fields are kept). Returns { updated, errors: [{ index, id?, message }] }.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
itemsYesPosts to update (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.14.0
    • addedInput schema / properties / items
      Added value: +{
      +  "description": "Posts to update (max 100)",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "advanced_robots": {
      +        "anyOf": [
      +          {
      +            "additionalProperties": false,
      +            "properties": {
      +              "max-image-preview": {
      +                "description": "none | standard | large",
      +                "type": "string"
      +              },
      +              "max-snippet": {
      +                "description": "e.g. -1 or 160",
      +                "type": [
      +                  "string",
      +                  "number"
      +                ]
      +              },
      +              "max-video-preview": {
      +                "description": "e.g. -1 or 30",
      +                "type": [
      +                  "string",
      +                  "number"
      +                ]
      +              }
      +            },
      +            "type": "object"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Advanced robots directives; other keys are dropped by the server. null deletes the stored value."
      +      },
      +      "breadcrumb_title": {
      +        "description": "Title used in breadcrumbs. null deletes the stored value.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "canonical": {
      +        "description": "Canonical URL. null deletes the stored value.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "description": {
      +        "description": "Meta description. null deletes the stored value.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "focus_keywords": {
      +        "anyOf": [
      +          {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Focus keywords, max 5 (extra ones are dropped). null deletes the stored value."
      +      },
      +      "id": {
      +        "description": "Post ID",
      +        "type": "integer"
      +      },
      +      "og_description": {
      +        "description": "Open Graph description. null deletes the stored value.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "og_image": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Open Graph image attachment ID. null deletes the stored value."
      +      },
      +      "og_title": {
      +        "description": "Open Graph title. null deletes the stored value.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "pillar_content": {
      +        "description": "Mark as pillar (cornerstone) content. null deletes the stored value.",
      +        "type": [
      +          "boolean",
      +          "null"
      +        ]
      +      },
      +      "robots": {
      +        "description": "Robots directives, comma separated (e.g. \"noindex,nofollow\"). null deletes the stored value.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "schema": {
      +        "anyOf": [
      +          {
      +            "anyOf": [
      +              {
      +                "additionalProperties": {},
      +                "type": "object"
      +              },
      +              {
      +                "type": "array"
      +              },
      +              {
      +                "type": "string"
      +              }
      +            ]
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Custom JSON-LD (object, array or JSON string); overrides schema_type. Invalid JSON is stored as []. null deletes the stored value."
      +      },
      +      "schema_type": {
      +        "description": "Schema type built from post data: BlogPosting, Article, NewsArticle, WebPage or Product. null deletes the stored value.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "seo_score": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Stored SEO score (0-100). null deletes the stored value."
      +      },
      +      "software_app": {
      +        "anyOf": [
      +          {
      +            "additionalProperties": {},
      +            "type": "object"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Per-post SoftwareApplication schema: { enabled, name, applicationCategory, operatingSystem, description, url, offers: [{ name, price, priceCurrency, url, unitText, unitCode }] (max 20), aggregateRating }. Omitted enabled = true. null deletes the stored value."
      +      },
      +      "title": {
      +        "description": "SEO title (template tokens like %title%, %sep%, %sitename% allowed). null deletes the stored value.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "twitter_card": {
      +        "anyOf": [
      +          {
      +            "enum": [
      +              "summary",
      +              "summary_large_image"
      +            ],
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Twitter card type; unset falls back to the default_twitter_card setting. null deletes the stored value."
      +      },
      +      "twitter_description": {
      +        "description": "Twitter description. null deletes the stored value.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "twitter_image": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Twitter image attachment ID. null deletes the stored value."
      +      },
      +      "twitter_title": {
      +        "description": "Twitter title. null deletes the stored value.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "id"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 100,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • removedInput schema / properties / updates
      Removed value: -{
      -  "additionalProperties": {},
      -  "description": "Bulk update payload (e.g. { posts: [{ id, ...meta }] })",
      -  "type": "object"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "site",
      -  "updates"
      -]New value: +[
      +  "site",
      +  "items"
      +]
  2. Addedv3.4.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries full weight, and it does disclose the two behaviors that matter most for a bulk mutation: destructive null semantics versus omitted-field preservation, and the { updated, errors: [{ index, id?, message }] } return shape. What it omits is atomicity – whether successfully validated items are written when other items fail is left to be inferred from the errors structure.

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?

Three tightly packed sentences: purpose and limit first, item contract second, return shape last. No filler, and the most decision-relevant information is front-loaded.

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?

With no output schema, the description compensates by describing the return payload, and it defines the item shape and size cap needed to call the tool correctly. The remaining gap is failure semantics – partial-success behavior and what to do with the errors array – which is important for a 100-item bulk mutation but at least hinted at by the return shape.

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% and every item field is documented there, including the null-deletes convention that the description repeats. The description's only added meaning is pointing at seo_update_post_seo as the authoritative field list, which helps but does not add per-parameter detail beyond the schema.

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, resource, scope and hard limit: "Bulk update SEO meta of up to 100 posts." The bulk framing plus the 100-item ceiling cleanly separates it from the single-post sibling seo_update_post_seo, which is named as the field reference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it (batching many posts at once) and gives the crucial per-item contract: fields follow seo_update_post_seo, null deletes, omission keeps. However, it never states an explicit alternative or condition (e.g. "use seo_update_post_seo for a single post") and says nothing about whether partial failures are acceptable or how to react to the errors array.

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