Skip to main content
Glama

Set the venue text and amenities

set_listing

Sets the description of the place shown at the top of the booking page, and the venue-wide amenities. Only the fields sent are changed. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>"
    },
    "name": "set_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
aboutNoUp to 1500 characters.
addressYesThe venue’s address name, the "name" in name.bookare.app.
amenitiesNoVenue amenity keys (the venue_amenities list of this venue’s stay options). Replaces the current list.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare mutation with no destruction or idempotency, so the description genuinely adds: 'Only the fields sent are changed' (partial update, omitted fields untouched), 'Acts on one venue, given its address and access key' (single-resource targeting plus credential requirement). It also flags the overwrite risk for amenities via schema wording. It does not explain what happens with unknown amenity keys or whether repeated identical calls are safe, leaving some ambiguity against idempotentHint=false.

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?

Three short sentences, front-loaded with the resource being changed, then the partial-update rule, then the scope. Nothing is repeated from the title and no sentence is padding.

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 mutation tool with no output schema and partial annotation coverage, the description covers the essentials: what changes, that changes are partial, the overwrite behavior of the amenities list, and that a single venue is targeted via credentials. Missing only edge-case behavior (invalid amenity keys, error/auth failure conditions) to be fully complete.

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 all four parameters are already documented, including that amenities replaces the current list. The description's 'Only the fields sent are changed' adds real meaning about the two optional fields and 'address and access key' clarifies the identification/auth pair, but stays at baseline-plus rather than defining syntax or valid key formats.

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 two concrete resources: the venue description text shown at the top of the booking page, and venue-wide amenities. That is far more specific than the tool name 'set_listing' would suggest. It does not, however, name the read counterpart get_listing or any sibling it might be confused with, so it falls short of full sibling differentiation.

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 rather than stated: an agent can infer this is the tool for changing the top-of-page description and amenity list of a single venue. There is no explicit when-to-use or when-not-to-use guidance, and no alternative (e.g. get_listing for reading, set_branding for other presentation fields) is named. 'Acts on one venue' does scope the call usefully but is not routing guidance.

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