Skip to main content
Glama

set_featured_image

DestructiveIdempotent

Assigns or updates the featured image for an existing WordPress post using its post ID and the media ID.

Instructions

Set featured image for existing post

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": {
      "post_id": "<post_id>",
      "media_id": "<media_id>"
    },
    "name": "set_featured_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesPost ID to update
media_idYesMedia ID for featured image

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already flag this as a non-read-only, destructive, idempotent write, so the safety profile is covered. However, the description never explains the destructive element that matters most here: that any previously set featured image is replaced, nor whether the media must already exist or what happens if it doesn't.

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?

A single front-loaded phrase with zero filler; the scope constraint (existing post) appears immediately after the action.

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?

For a two-parameter tool with full schema coverage, rich annotations, and no output schema, the definition is close to sufficient. It falls short only on the replacement semantics of a destructive write, which an agent would want before calling it.

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 coverage is 100% and both parameters are documented in the schema, so the description is not required to carry parameter meaning. It adds nothing beyond the schema, which is the baseline-3 case.

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 and resource: setting a featured image on a post that already exists. The qualifier "existing post" implicitly contrasts it with sibling create_post_with_featured_image, though it never names that alternative.

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 or when-not guidance and no named alternative. An agent must infer from "existing post" that new posts should go through a creation tool instead.

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