Skip to main content
Glama
ArsNovaSingers

ars-nova-wordpress-mcp

Official

Audit Alt Text

wp_audit_alt_text
Read-onlyIdempotent

Audit your WordPress media library to find images missing alt text. Scan in batches of up to 500 items, returning a paginated list of media IDs and titles for accessibility fixes.

Instructions

Scan the media library and report which IMAGE items are missing alt text. Skips non-image media (video/audio/file). Designed to be paginated for large libraries — start at offset 0, then re-run with the returned next_offset.

Args:

  • scan_limit (number): How many media items to scan in this call, 1-500. Default 100.

  • limit (number): How many missing-alt items to return in the result. Default 20.

  • offset (number): Pagination offset INTO THE MEDIA LIBRARY (not into the missing list). Default 0.

  • response_format (enum): markdown | json. Default 'markdown'.

Returns: WPAltTextAuditResult object with shape: { "total_media_scanned": number, "total_images_scanned": number, "missing_alt_count": number, "missing_alt_items": [ { "id": number, "title": string, "source_url": string, "attached_to_id": number } ], "has_more": boolean, "next_offset": number // Present if has_more }

Note: missing_alt_count is the count WITHIN this scan window only. Re-run with the returned next_offset to continue scanning the rest of the library.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results to return (1-100). Default 20.
offsetNoNumber of results to skip for pagination. Default 0.
scan_limitNoHow many media items to scan in this call (1-500). Default 100.
response_formatNoOutput format: 'markdown' for human-readable, 'json' for machine-readable.markdown
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses important behavioral nuances: it skips non-image media, offsets are into the media library rather than the missing list, and the missing_alt_count is scoped to the current scan window only. This adds significant value and prevents misinterpretation.

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?

The description is well-structured with clear sections for Args and Returns, using bullets and a code block for readability. It is a bit long but every sentence contributes essential information, avoiding fluff.

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

Completeness5/5

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

Despite having no output schema, the description provides a full return shape, explains pagination flow, and covers scoping behavior. Combined with rich annotations, this gives the agent everything needed to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions are already comprehensive (100% coverage), but the description adds crucial semantics: it explicitly clarifies that 'offset' paginates through the media library, not the result set, and explains the relationship between scan_limit and limit. This goes beyond the schema's generic wording.

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 tool's function: 'Scan the media library and report which IMAGE items are missing alt text.' It uses a specific verb ('Scan') and resource ('media library'), and explicitly restricts to images, distinguishing it from sibling media tools like wp_list_media.

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?

Provides clear guidance on when to use the tool (to audit missing alt text) and how to paginate large libraries by starting at offset 0 and following next_offset. It does not explicitly name alternatives or exclusions, but the context is obvious enough to infer appropriate usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ArsNovaSingers/ars-nova-wordpress-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server