Skip to main content
Glama
l-margiela

OLX MCP Server

by l-margiela
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.9

  • Disambiguation5/5

    The two tools have clearly distinct purposes: one is for searching listings with filters, the other for retrieving details of a specific listing. There is no ambiguity between discovering and inspecting.

    Naming Consistency5/5

    Both tool names follow the same verb_noun pattern in camelCase (searchListings, getListingDetails). The style is consistent and predictable.

    Tool Count3/5

    With only two tools, the server feels thin for the apparent scope of a marketplace data access layer, but the two tools cover the primary discovery and detail workflows, making the count borderline.

    Completeness4/5

    The tool surface covers the essential read-only workflows for a classifieds platform: searching for listings and viewing full details. Minor gaps exist, such as lack of category or seller list endpoints, but agents can likely work around these with search filters.

  • Average 3.2/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • 0 of 1 community issues answered or closed in the last 6 months
    • 6 commits in the last 12 weeks
    • Last stable release on
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI is failing

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior2/5

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

    With no annotations provided, the description carries the full burden of disclosing behavior. It only states 'Search for listings' and lists filters, without revealing pagination behavior, response format, rate limits, or any side effects. It is not misleading but lacks essential behavioral context.

    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?

    The description is a single sentence, front-loaded with the core action. It is fairly concise, though slightly run-on due to the enumeration of filters and domains, which could be restructured for readability without adding length.

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

    Completeness2/5

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

    For a tool with 9 parameters, no output schema, and no annotations, the description is too sparse. It omits that domain is required, does not mention the valid enum values, does not address pagination limits or sorting, and gives no indication of the response structure. This leaves significant gaps for an agent to correctly use the tool.

    Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

    Parameters2/5

    Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

    The description mentions query, category, location, and price range, which map partially to schema properties. However, it does not clarify that domain is required, nor does it mention pagination (page, limit) or sortBy. With 0% schema description coverage, this partial compensation is insufficient.

    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 clearly states the tool searches for listings on specific OLX domains with filters, which is a specific verb+resource. It distinguishes itself from sibling getListingDetails by focusing on search rather than fetching details of a single listing.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines2/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    No explicit guidance on when to use this tool versus the sibling getListingDetails. The description implies general search usage but does not state when to choose this over alternatives or what scenarios it is suitable for.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

  • Behavior3/5

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

    With no annotations, the description carries the burden. It discloses the tool's scope (domains) and included data, but omits behavioral aspects like request handling, error behavior, authentication, or how optional flags affect results. Since it is a read operation, the impact is moderate but still incomplete.

    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 a single sentence, front-loaded with the main purpose. The parenthetical domain list adds practical specificity without unnecessary length, and every word contributes.

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

    Completeness2/5

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

    Given four parameters, no output schema, and no annotations, the description is too sparse. It fails to describe the effect of optional flags, the return format, or any caveats, leaving significant gaps for an agent to invoke the tool correctly.

    Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

    Parameters1/5

    Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

    Schema description coverage is 0%, and the description does not explain any of the four parameters. The words 'images' and 'seller info' loosely relate to the boolean flags, but no explicit linkage or meaning is provided, leaving the agent without enough guidance to set includeImages or includeSellerInfo correctly.

    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 clearly states the verb 'Get' and resource 'detailed information about a specific OLX listing', enumerates supported domains, and lists included content (description, seller info, images). The phrase 'specific listing' distinguishes it from the sibling tool 'searchListings'.

    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 clearly implies use when a specific listing's details are needed, contrasting with search. However, it does not explicitly mention when not to use it or reference the alternative 'searchListings', so no explicit exclusions are provided.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

olx-mcp MCP server

Copy to your README.md:

Score Badge

olx-mcp MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/l-margiela/olx-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server