Skip to main content
Glama
ilhankilic

YaparAI MCP Server

by ilhankilic

send_shipping_info

Send tracking details and shipping status to customers via the same social media platform they contacted you on, providing immediate delivery updates.

Instructions

Send shipping/tracking information to a customer via social media.

Automatically sends a tracking message through the same social platform the customer contacted you on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYesCustomer ID to notify
carrierYesShipping carrier (e.g., "Yurtici", "Aras", "PTT", "MNG", "DHL")
tracking_codeYesPackage tracking number
org_idNoOrganization ID (uses YAPARAI_ORG_ID env var if not provided)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async function `send_shipping_info` that executes the tool logic. It accepts customer_id, carrier, tracking_code, and optional org_id, resolves the org ID, and delegates to the API client's `crm_send_shipping` method.
    async def send_shipping_info(
        customer_id: str,
        carrier: str,
        tracking_code: str,
        org_id: str | None = None,
    ) -> dict:
        """
        Send shipping/tracking information to a customer via social media.
    
        Automatically sends a tracking message through the same social
        platform the customer contacted you on.
    
        Args:
            customer_id: Customer ID to notify
            carrier: Shipping carrier (e.g., "Yurtici", "Aras", "PTT", "MNG", "DHL")
            tracking_code: Package tracking number
            org_id: Organization ID (uses YAPARAI_ORG_ID env var if not provided)
    
        Returns:
            Dict with delivery status, carrier, and tracking_code.
        """
        oid = resolve_org_id(org_id)
        client = YaparAIClient()
        return await client.crm_send_shipping(oid, customer_id, {
            "carrier": carrier,
            "tracking_code": tracking_code,
        })
  • The `crm_send_shipping` method on YaparAIClient that sends a POST request to the enterprise API endpoint `/api/enterprise/orgs/{org_id}/crm/customers/{customer_id}/send-shipping` with the carrier and tracking_code payload.
    async def crm_send_shipping(self, org_id: str, customer_id: str, payload: dict) -> dict:
        """Send shipping/tracking notification."""
        return await self._request(
            "POST",
            f"/api/enterprise/orgs/{org_id}/crm/customers/{customer_id}/send-shipping",
            json=payload,
        )
  • Import of `send_shipping_info` from `yaparai.tools.crm` into the server module.
    send_shipping_info,
  • Registration of `send_shipping_info` as an MCP tool via `mcp.tool(send_shipping_info)`.
    mcp.tool(send_shipping_info)
  • Call to `resolve_org_id(org_id)` which resolves the organization ID from the parameter or YAPARAI_ORG_ID environment variable.
    oid = resolve_org_id(org_id)
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses automatic platform selection, but omits details like permissions, potential failures, or prerequisites.

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?

Two concise sentences, front-loaded with main action, no redundant words.

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 and schema coverage is high, the description is nearly complete. Minor gap: doesn't specify if customer must have an existing conversation.

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 baseline is 3. The description adds minimal context beyond the schema (e.g., platform selection), not enough to raise the score.

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 sends shipping/tracking information via social media and automatically selects the platform based on customer contact, which is a specific verb+resource and distinguishes it from generic messaging siblings.

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?

The description implies when to use (when you have shipping tracking to send) but lacks explicit when-not-to-use or alternatives, though context is clear.

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