Skip to main content
Glama

PIN 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. 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

A4/5.0
Behavior4/5

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

Annotations already establish read-only and closed-world behavior. The description adds meaningful content scope by stating which listing fields are included and explicitly excluding contact data, routing that need to reveal_contact. Additional auth or rate-limit details are not necessary here.

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?

It is two short sentences, front-loaded with the returned content and then the exclusion/alternative. Every phrase contributes to scope or routing.

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?

The tool is simple, has an output schema, and has complete parameter documentation, so the description mainly needs to clarify scope. It does that well for included fields and contact exclusion, though it could more explicitly orient use relative to search_adverts.

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 advert_id and language are fully documented in the schema. The description adds no parameter-level meaning beyond what the schema already provides, which sets the baseline at 3.

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?

The description names the resource and enumerates returned fields (description, attributes, photos, seller), and it explicitly excludes contacts, which distinguishes it from reveal_contact. It lacks an explicit retrieval verb, so it is slightly less crisp than an ideal verb+resource statement.

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?

It gives a direct when-not-to-use rule and alternative: contacts are not included, so use reveal_contact. It does not explicitly state the primary use case or point to search_adverts for obtaining advert_id, though the parameter schema covers that.

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