Skip to main content
Glama

update_listing

Idempotent

Edit fields (title, description, price, currency, location, details) on one of the USER'S OWN listings, identified by listing_id. Only the owner can edit; vertical/intent_type/role are fixed (publish a new listing to change those). Editing is free (no credit charge). Changing the title, description, location or details re-triggers AI moderation: the listing returns to 'pending' and is offline until cleared. Price/currency-only edits stay live. On a listing published by an assistant, price, currency and the money details are locked and rejected with price_locked.

Input Schema

NameRequiredDescriptionDefault
priceNoNew asking price as a plain number. Rejected with price_locked on a listing published by an assistant. To change a salary range use details.salary_min and details.salary_max. Example: 950.
titleNoNew headline, 3-200 characters. Returns the listing to "pending". Example: "Two-bedroom flat near the river".
detailsNoVertical-specific attributes to change. Only these exact keys for the listing's vertical are accepted; any other key is rejected with an error. career: organization_name, employment_type, salary_min, salary_max, years_experience. real_estate: property_room_count, m2_gross, m2_net, building_age, floor_number, heating_type, deposit, dues, is_furnished, is_student_friendly, is_credit_eligible, tapu_status. vehicle: brand, model, vehicle_model_year, vehicle_mileage_km, fuel_type, gear_type, color, damage_status, daily_price, deposit. service: service_category. employment_type is one of full_time, part_time, contract, freelance, internship. is_furnished, is_student_friendly and is_credit_eligible are booleans. Any details edit returns the listing to "pending", so it goes offline until AI moderation clears it. On a listing published by an assistant, salary_min, salary_max, deposit and daily_price are locked and rejected with price_locked. Example: { "m2_gross": 90 }.
currencyNoNew ISO-4217 currency code. Rejected with price_locked on a listing published by an assistant. Example: "EUR".
locationNoNew listing coordinates { lat, lon }. Moving a listing re-triggers AI moderation — it returns to "pending" until cleared. Example: { "lat": 48.85, "lon": 2.35 }.
listing_idYesListing id, taken from the `id` field of search_listings, semantic_search or list_my_listings results. Example: "adzuna-us-5947308680".
descriptionNoNew full listing text, up to 5000 characters. Returns the listing to "pending". Example: "Bright flat on the third floor, five minutes from the metro."

Output Schema

NameRequiredDescriptionDefault
listingYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed9 schema fields changed
    • addedInput schema / properties / currency / description
      Added value: +"New ISO-4217 currency code. Rejected with price_locked on a listing published by an assistant. Example: \"EUR\"."
    • addedInput schema / properties / description / description
      Added value: +"New full listing text, up to 5000 characters. Returns the listing to \"pending\". Example: \"Bright flat on the third floor, five minutes from the metro.\""
    • addedInput schema / properties / details / description
      Added value: +"Vertical-specific attributes to change. Only these exact keys for the listing's vertical are accepted; any other key is rejected with an error. career: organization_name, employment_type, salary_min, salary_max, years_experience. real_estate: property_room_count, m2_gross, m2_net, building_age, floor_number, heating_type, deposit, dues, is_furnished, is_student_friendly, is_credit_eligible, tapu_status. vehicle: brand, model, vehicle_model_year, vehicle_mileage_km, fuel_type, gear_type, color, damage_status, daily_price, deposit. service: service_category. employment_type is one of full_time, part_time, contract, freelance, internship. is_furnished, is_student_friendly and is_credit_eligible are booleans. Any details edit returns the listing to \"pending\", so it goes offline until AI moderation clears it. On a listing published by an assistant, salary_min, salary_max, deposit and daily_price are locked and rejected with price_locked. Example: { \"m2_gross\": 90 }."
    • addedInput schema / properties / listing_id / description
      Added value: +"Listing id, taken from the `id` field of search_listings, semantic_search or list_my_listings results. Example: \"adzuna-us-5947308680\"."
    • changedInput schema / properties / location / description
      Previous value: -"New listing coordinates { lat, lon }. Moving a listing re-triggers AI moderation — it returns to \"pending\" until cleared."New value: +"New listing coordinates { lat, lon }. Moving a listing re-triggers AI moderation — it returns to \"pending\" until cleared. Example: { \"lat\": 48.85, \"lon\": 2.35 }."
    • addedInput schema / properties / location / properties / lat / description
      Added value: +"Latitude in decimal degrees. Example: 48.85."
    • addedInput schema / properties / location / properties / lon / description
      Added value: +"Longitude in decimal degrees. Example: 2.35."
    • addedInput schema / properties / price / description
      Added value: +"New asking price as a plain number. Rejected with price_locked on a listing published by an assistant. To change a salary range use details.salary_min and details.salary_max. Example: 950."
    • addedInput schema / properties / title / description
      Added value: +"New headline, 3-200 characters. Returns the listing to \"pending\". Example: \"Two-bedroom flat near the river\"."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "listing": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "currency": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "price": {
      +          "anyOf": [
      +            {
      +              "type": "number"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "status": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "title": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "url": {
      +          "type": "string"
      +        },
      +        "vertical": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "listing"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the moderation lifecycle: title/description/location/details edits return the listing to 'pending' and take it offline until AI moderation clears it, while price/currency-only edits stay live. It adds ownership constraints, the no-credit-charge fact, and the price_locked rejection rule for assistant-published listings — exactly the behavioral context a mutation tool needs.

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?

Front-loaded with purpose, then consequences, then lock rules — a logical order with no filler. It runs several sentences, but nearly every one carries a distinct operational fact (ownership, free, moderation, price_locked).

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?

For a 7-parameter nested mutation tool with a rich schema and output schema, the description covers everything the schema cannot: ownership requirement, moderation/offline consequence, cost, and the assistant-published lock behavior. Nothing an agent needs before calling is missing.

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 coverage is 100%, so the baseline is 3; the description earns extra by stating which parameter groups trigger re-moderation versus which stay live, and by explaining the price_locked rejection semantics per parameter. It doesn't duplicate the key lists already in the details schema, which is appropriate.

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 opening sentence names a specific verb (edit), an explicit resource (one of the USER'S OWN listings), the editable field set, and the identifier (listing_id). It also states the boundary condition — vertical/intent_type/role are fixed and require a new listing — which separates it from create_listing.

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?

Clear context: only the owner can edit, and changes to vertical/intent_type/role must go through publishing a new listing. It does not route away from close siblings like update_listing_images or set_listing_status, so an agent must infer that images and status transitions belong elsewhere.

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