Skip to main content
Glama

seo_list_posts_seo

Lists published posts with their SEO metadata, titles, URLs, and translations, newest ID first, so you can audit SEO coverage and filter by site, language, or post type.

Instructions

List SEO meta of published posts, newest ID first: [{ id, title, url, seo, language?, translations? }].

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

Input Schema

NameRequiredDescriptionDefault
langNoPolylang language code (default: every language; ignored without Polylang)
pageNoPage number (default 1)
siteYesSite id (see list_sites)
has_seoNotrue = only posts with an SEO title set, false = only posts without one (default: all)
per_pageNoItems per page, 1-100 (default 50)
post_typeNoPost type (default post)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.14.0
    • addedInput schema / properties / has_seo
      Added value: +{
      +  "description": "true = only posts with an SEO title set, false = only posts without one (default: all)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "Polylang language code (default: every language; ignored without Polylang)",
      +  "type": "string"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Page number (default 1)",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / params
      Removed value: -{
      -  "additionalProperties": {
      -    "type": [
      -      "string",
      -      "number"
      -    ]
      -  },
      -  "description": "Query params (page, per_page, post_type, search, ...)",
      -  "type": "object"
      -}
    • addedInput schema / properties / per_page
      Added value: +{
      +  "description": "Items per page, 1-100 (default 50)",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / post_type
      Added value: +{
      +  "description": "Post type (default post)",
      +  "type": "string"
      +}
  2. Addedv3.4.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that only published posts are listed, results are ordered by newest ID first, and the return fields include id, title, url, seo, language, and translations. However, it does not describe pagination behavior, read-only safety, permissions, or how filters like has_seo behave in practice.

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 front-loaded sentence with no wasted wording. It packs the operation, scope, ordering, and return shape efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is adequate for a moderately complex listing tool with six parameters and no output schema, and it does provide the return shape and ordering. However, with no annotations and no usage guidance, it leaves gaps around when to use this tool versus alternatives, pagination behavior, and permission expectations.

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 the input schema already documents all six parameters and their defaults. The description adds no parameter-specific meaning beyond the schema baseline, so a 3 is appropriate.

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?

The description states a specific verb and resource: 'List SEO meta of published posts,' and adds ordering ('newest ID first') plus an output shape. It clearly tells an agent this is a list operation over post SEO metadata, though it does not explicitly differentiate from siblings like seo_get_post_seo or wp_list_posts.

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 explicit when-to-use guidance, no alternatives named, and no exclusions or prerequisites. The phrase 'published posts' implies a scope, but an agent is not told when to choose this over seo_get_post_seo or another listing tool.

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