Fetch public Airbnb room calendar availability by room ID. Parses bootstrap data to return monthly calendar hints as clean JSON.
Get Airbnb room calendar. Returns public calendar month hints parsed from Airbnb room bootstrap data.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Room id |
Changes observed during successful MCP inspections.
v1.6.0v1.6.0v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description bears full burden. It states the tool returns 'public calendar month hints parsed from Airbnb room bootstrap data', indicating a read-only operation. However, it does not disclose potential side effects, authentication needs, or rate limits, which is acceptable for a simple retrieval tool but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, with the first sentence stating the primary purpose and the second adding detail. It is front-loaded, concise, and contains no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description is adequate but lacks details on the return format or what 'calendar month hints' entail. More context on the output structure would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers the single parameter 'id' with description 'Room id', achieving 100% coverage. The description adds no additional meaning beyond this, so a baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool gets the Airbnb room calendar and returns 'public calendar month hints'. The verb 'Get' and resource 'Airbnb room calendar' are specific, and it distinguishes itself from sibling tools like airbnb_room (room details) and airbnb_room_reviews (reviews).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when needing calendar data, but does not explicitly state when to use this tool versus alternatives like airbnb_room. No exclusion or prerequisite information is provided, relying on the tool's name and context for differentiation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.