Skip to main content
Glama

Avito Seller

run_avito_sellers
Read-onlyIdempotent

Get an Avito seller (brand page) by slug or URL: name, type, rating, review count, followers, active listing count, registration date and badges. Flat 5 points per successful run.

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": {
      "seller": "<seller>"
    },
    "name": "run_avito_sellers"
  }
}

Input Schema

NameRequiredDescriptionDefault
sellerYesBrand slug or URL. e.g. steve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, open-world, non-destructive operation. The description adds useful behavioral detail beyond annotations by stating the flat 5-point cost per successful run and listing the fields returned, though it does not mention rate limits or error behavior.

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?

The description is compact and front-loaded: it states the operation, input format, and returned fields without filler. The cost sentence is short and relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by listing the seller fields returned. Annotations cover the safety profile, the sole parameter is fully documented, and the cost is disclosed, leaving no major gap for an agent invoking this tool.

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 single 'seller' parameter is fully documented in the schema with an example. The description restates that the input can be a slug or URL but adds no additional syntax or formatting guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Get an Avito seller (brand page)'. It also identifies the input form ('by slug or URL') and enumerates the returned seller fields, making it clearly distinct from sibling item/search tools.

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?

It implies usage by explaining that the tool retrieves a seller by slug or URL, but it does not explicitly state when to choose this over related tools such as run_avito_items or run_avito_items_search. The intended context is clear enough, but alternatives are left to inference.

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.