Skip to main content
Glama
ilhankilic

YaparAI MCP Server

by ilhankilic

list_competitors

Retrieve a list of competitors tracked by your organization, including website performance, social media metrics, and marketplace pricing data.

Instructions

List competitors tracked under your organization.

Competitor tracking includes website crawling (PageSpeed, SEO), social media metrics (followers, engagement), and marketplace product prices (Hepsiburada, Trendyol).

Requires enterprise subscription with an org-bound API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 50)
offsetNoPagination offset
org_idNoOptional — override the org bound to the API key

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler function for the list_competitors tool. Defines the async function with parameters (limit, offset, org_id) and calls the client method enterprise_list_competitors to fetch competitor data from the API.
    async def list_competitors(
        limit: int = 50,
        offset: int = 0,
        org_id: str | None = None,
    ) -> dict:
        """
        List competitors tracked under your organization.
    
        Competitor tracking includes website crawling (PageSpeed, SEO),
        social media metrics (followers, engagement), and marketplace
        product prices (Hepsiburada, Trendyol).
    
        Requires enterprise subscription with an org-bound API key.
    
        Args:
            limit: Max results (default 50)
            offset: Pagination offset
            org_id: Optional — override the org bound to the API key
    
        Returns:
            {"competitors": [...], "total": N} — each competitor with
            id, name, website, notes, created_at.
        """
        client = YaparAIClient()
        return await client.enterprise_list_competitors(limit=limit, offset=offset, org_id=org_id)
  • HTTP client helper method enterprise_list_competitors that sends a GET request to /v1/public/enterprise/competitors with optional X-Organization-Id header and pagination params.
    async def enterprise_list_competitors(
        self, limit: int = 50, offset: int = 0, org_id: str | None = None
    ) -> dict:
        """List competitors under the org bound to the API key."""
        headers = {"X-Organization-Id": org_id} if org_id else {}
        return await self._request(
            "GET",
            "/v1/public/enterprise/competitors",
            params={"limit": limit, "offset": offset},
            headers=headers,
        )
  • Registration of list_competitors as an MCP tool via mcp.tool(list_competitors).
    mcp.tool(list_competitors)
  • Import of list_competitors from yaparai.tools.enterprise module into the server module.
    from yaparai.tools.enterprise import (
        list_competitors,
        get_competitor,
        compare_competitors,
        list_org_products,
        create_org_product,
        update_product_stock,
    )
Behavior2/5

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

No annotations are provided, so description carries full burden. It states the tool lists competitors (read operation) but does not explicitly confirm non-destructive behavior, rate limits, data freshness, or any side effects. This is insufficient for a standalone disclosure.

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?

Three sentences, each adding value: purpose, scope of tracking, and prerequisites. No fluff, front-loaded with main action.

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?

Given output schema exists, return format is covered. Description covers purpose, scope, and requirements. Could briefly mention pagination behavior (e.g., ordering) but otherwise complete for a listing 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?

Input schema has 100% description coverage, so baseline is 3. The description adds no additional meaning beyond the schema; it only implicitly mentions org_id override. No extra context for limit/offset.

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?

Description clearly states 'List competitors tracked under your organization' with specific verb and resource. It distinguishes from siblings like 'get_competitor' and 'compare_competitors' by detailing what competitor tracking includes (crawling, social, marketplace).

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?

Description mentions prerequisites ('enterprise subscription with org-bound API key') but does not explicitly guide when to use this tool versus alternatives like get_competitor or compare_competitors. Usage is implied but not contrasted.

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

Install Server

Other Tools

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/ilhankilic/yaparai-mcp'

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