Fetch an Airbnb public host profile by numeric ID to get display name, Superhost and identity-verification status, location, bio, tenure, guest-review count, and listing count.
Get Airbnb host profile. Returns an Airbnb public host profile — display name, Superhost and identity-verification status, location, bio, hosting tenure, total guest-review count, and total listing count.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Host id (numeric) |
Changes observed during successful MCP inspections.
v1.6.0v1.6.0v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the behavioral load. 'Get' and 'public host profile' imply a non-destructive read, and the enumerated fields disclose what data is exposed, which is real value. It stops short of stating behavior for a missing/invalid host id or whether results are cached or rate-limited.
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?
Two sentences, both earning their place: the first states the action, the second front-loads the return payload. No filler or redundancy.
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?
With no output schema and only one input param, the field enumeration is the key addition and it is present. The definition is essentially complete for a simple lookup, missing only id-sourcing and failure-mode notes.
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?
Only one parameter with 100% schema description coverage ('Host id (numeric)'), so the schema already documents it fully. The description adds no format or sourcing detail for the id, so the baseline 3 applies.
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?
States a specific verb ('Get') and resource ('Airbnb host profile'), then enumerates the returned fields, so the purpose is unambiguous. It does not, however, distinguish itself from sibling host-scoped tools such as airbnb_host_listings or airbnb_host_reviews, leaving the agent to infer the split.
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?
There is no when-to-use guidance, no mention of alternatives, and no statement of where the required host id comes from (e.g. airbnb_room or airbnb_search). Usage is only implied by the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.