Skip to main content
Glama

Bazaraki classifieds

Listing details

get_advert
Read-only

Listing details: description, attributes, photos, seller. No contacts: use reveal_contact.

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": {
      "advert_id": "<advert_id>"
    },
    "name": "get_advert"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of listing texts: one of en, el. Default en.
advert_idYesadvert_id from search_adverts, or a listing url.

Output Schema

NameRequiredDescriptionDefault
urlYes
priceNo
titleYes
photosNo
sellerYes
locationNo
advert_idYesPass to reveal_contact as is.
publishedNo
attributesNo
price_noteNo
descriptionNo
category_pathNo
contact_channelsNoChannels the seller accepts; call reveal_contact to get them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description's useful addition is the scope boundary that contact data is excluded, but it says nothing about failure behavior for an unknown advert_id or about rate limits, so the extra context is modest.

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?

Two short clauses, front-loaded with what the tool returns before the exclusion. Every phrase carries information, though the telegraphic fragment style leaves the core action slightly implicit.

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?

An output schema exists, so return values need not be described, and the description covers scope plus the key exclusion for an otherwise simple two-parameter read tool. Only minor behavioral detail, such as handling of a missing or invalid advert_id, is absent.

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%, and the schema itself explains that advert_id can come from search_adverts or be a listing url, and that language accepts en/el. The description adds no meaning beyond that, so the baseline 3 applies.

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?

Names the resource (a listing) and enumerates what it returns: description, attributes, photos, seller. That is specific enough for an agent to know it is a single-listing detail fetch, though the retrieval verb is only implied by the noun phrase and the advert_id parameter.

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 'No contacts: use reveal_contact' clause is a genuine routing instruction that tells the agent when to pick a sibling instead. However, there is no guidance on when to use this versus search_adverts, nor any stated prerequisites, so the guidance is partial rather than comprehensive.

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