Skip to main content
Glama

media_scan_urls

Scans WordPress content and options for links to outdated image URLs, such as .jpg files replaced by .webp, up to a set row limit. Read-only.

Instructions

Scan content and options for links to old image URLs (e.g. .jpg that became .webp), reading at most limit rows. Read-only.

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": "media_scan_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
limitNoMost links checked and rows read, 1..5000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.5/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 usefully discloses that the tool is read-only and caps how many rows/links are read, but it does not explain the result shape, permissions, or whether the scan only reports links versus modifying anything.

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?

Two short sentences with no filler. The scan target and bound are front-loaded, and the trailing "Read-only" is important context.

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 tool is simple (two parameters, no output schema), but without an output schema the description should say more about what a scan returns. Scope and the row limit are covered, yet result format and permissions are omitted.

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 schema already defines both parameters. The description reinforces the limit semantics with "reading at most limit rows," but adds no site-id detail or format beyond what the schema provides.

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, "Scan," and a specific resource, "content and options for links to old image URLs," with an example and a row bound. It does not explicitly contrast with sibling scan tools such as mcp_scan_uploads, but the target domain is clear enough to distinguish it.

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?

Usage is implied: call this when looking for legacy image URL references in content and options, and it is safe because it is read-only. There is no explicit when-not guidance, no named alternative, and no prerequisite or follow-up guidance.

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