Skip to main content
Glama
ilhankilic

YaparAI MCP Server

by ilhankilic

get_competitor

Retrieve detailed information about a specific competitor using its unique ID. Enables competitive analysis for social media and content strategy.

Instructions

Get detailed info for a single competitor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
competitor_idYesUUID from list_competitors results
org_idNoOptional — override the org bound to the API key

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `get_competitor` async function is the tool handler. It takes a competitor_id (UUID) and optional org_id, creates a YaparAIClient, and delegates to client.enterprise_get_competitor().
    async def get_competitor(
        competitor_id: str,
        org_id: str | None = None,
    ) -> dict:
        """
        Get detailed info for a single competitor.
    
        Args:
            competitor_id: UUID from list_competitors results
            org_id: Optional — override the org bound to the API key
    
        Returns:
            Competitor profile including name, website, industry, notes.
        """
        client = YaparAIClient()
        return await client.enterprise_get_competitor(competitor_id, org_id=org_id)
  • The function signature defines the schema: competitor_id (str, required) and org_id (str | None, optional). The docstring describes the return as a competitor profile dict with name, website, industry, notes.
    async def get_competitor(
        competitor_id: str,
        org_id: str | None = None,
    ) -> dict:
        """
        Get detailed info for a single competitor.
    
        Args:
            competitor_id: UUID from list_competitors results
            org_id: Optional — override the org bound to the API key
    
        Returns:
            Competitor profile including name, website, industry, notes.
        """
        client = YaparAIClient()
        return await client.enterprise_get_competitor(competitor_id, org_id=org_id)
  • Import of get_competitor from yaparai.tools.enterprise.
    from yaparai.tools.enterprise import (
        list_competitors,
        get_competitor,
        compare_competitors,
        list_org_products,
        create_org_product,
        update_product_stock,
    )
  • Registration via mcp.tool(get_competitor) on line 178, registering it as an MCP tool under 'Enterprise: Competitor Analysis + Product Catalog'.
    # Enterprise: Competitor Analysis + Product Catalog (v0.5.0) (6)
    mcp.tool(list_competitors)
    mcp.tool(get_competitor)
    mcp.tool(compare_competitors)
    mcp.tool(list_org_products)
    mcp.tool(create_org_product)
    mcp.tool(update_product_stock)
  • The underlying HTTP client method `enterprise_get_competitor` that makes the GET request to /v1/public/enterprise/competitors/{competitor_id} with optional X-Organization-Id header.
    async def enterprise_get_competitor(
        self, competitor_id: str, org_id: str | None = None
    ) -> dict:
        headers = {"X-Organization-Id": org_id} if org_id else {}
        return await self._request(
            "GET",
            f"/v1/public/enterprise/competitors/{competitor_id}",
            headers=headers,
        )
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, permissions, or idempotency. For a read operation, information about caching or data freshness would be helpful.

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?

Single sentence is concise and front-loaded. However, it could incorporate more detail without losing conciseness, such as mentioning the source of competitor_id.

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

Completeness3/5

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

Given the presence of an output schema and only two parameters, the description is minimally adequate. Missing behavioral transparency and usage guidelines, but the core purpose is clear.

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 the description does not add significant meaning beyond what is already in the schema. Baseline 3 is appropriate.

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 action 'Get detailed info' and the resource 'a single competitor'. It effectively distinguishes from sibling tools like 'list_competitors' and 'compare_competitors' by focusing on a single entity.

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 alternatives. The schema implies using competitor_id from list_competitors, but the description lacks direct context or exclusion criteria.

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