Skip to main content
Glama

Yuppsy

property_set_images

Destructive

Set images for an existing property. This will clear all existing images and add the new ones. The first image will be set as the cover image. If successful, it returns the IDs of the newly added images. data => { id = 'image id', uriL = 'image uri L' }

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": {
      "data": "<data>"
    },
    "name": "property_set_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe property image data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description corroborates that with concrete detail: all existing images are cleared, the first element becomes the cover image, and the call returns the new image IDs. The cover-image ordering rule and the return payload are real added value, especially since there is no output schema. It does not mention failure behavior or whether the property must be empty/published, so it is not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first three sentences are front-loaded and each earns its place. The final pseudo-shape line is unexplained noise that contradicts the schema's property names and should have been removed or rewritten.

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?

For a destructive, nested-object tool with no output schema, the description covers replacement semantics, cover-image selection, and return values — the essentials. It omits error/failure behavior and any precondition on the target property, which is a modest gap rather than a blocker.

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%, so the baseline is 3, but the description does add one genuinely useful semantic: array order determines the cover image. That gain is offset by the trailing "data => { id = 'image id', uriL = 'image uri L' }" snippet, which does not match the schema's actual fields (imageUriL, imageUriS, propertyId) and reads as a confusing or stale shape hint.

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 ("Set images for an existing property") and clarifies the operation is a wholesale replacement rather than an append, which implicitly separates it from property_insert_single_image. It does not name any sibling explicitly, so it stops short of a 5.

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 conveys the key selection context — this replaces the entire image set on an already-existing property — which is the main thing an agent needs to know before choosing it. However, it never states when NOT to use it or points at the single-image/delete alternatives that appear among siblings, leaving the agent to infer routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources