Skip to main content
Glama
ilhankilic

YaparAI MCP Server

by ilhankilic
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

list_organizations

List organizations you belong to on YaparAI. Get organization IDs, names, and your role to use with enterprise tools.

Instructions

List your organizations on YaparAI.

Returns organizations you're a member of, with their IDs, names, and your role. Use the org ID for enterprise tools (social media, CRM, chatbots). You can set YAPARAI_ORG_ID env var to skip passing org_id to every call. No credits charged.

Returns: List of organizations with id, name, role, and member count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/yaparai/tools/organizations.py:8-22 (handler)
    The actual tool handler for list_organizations. Creates a YaparAIClient and calls client.list_organizations().
    async def list_organizations() -> dict:
    """
    List your organizations on YaparAI.

    Returns organizations you're a member of, with their IDs, names,
    and your role. Use the org ID for enterprise tools (social media,
    CRM, chatbots). You can set YAPARAI_ORG_ID env var to skip
    passing org_id to every call.
    No credits charged.

    Returns:
        List of organizations with id, name, role, and member count.
    """
    client = YaparAIClient()
    return await client.list_organizations()
  • src/yaparai/server.py:154-154 (registration)
    Registration of list_organizations as an MCP tool via mcp.tool().
    mcp.tool(list_organizations)
  • src/yaparai/server.py:67-67 (registration)
    Import of list_organizations from yaparai.tools.organizations.
    from yaparai.tools.organizations import list_organizations
  • src/yaparai/client.py:201-203 (helper)
    The low-level HTTP client method that sends a GET request to /api/enterprise/organizations.
    async def list_organizations(self) -> list:
    """List user's organizations."""
    return await self._request("GET", "/api/enterprise/organizations")
  • src/yaparai/tools/_org.py:6-18 (helper)
    Helper that references list_organizations in its error message when no org ID is found.
    def resolve_org_id(org_id: str | None = None) -> str:
    """Return the org_id from parameter or YAPARAI_ORG_ID env var.

    Raises ValueError if neither is set.
    """
    oid = org_id or YAPARAI_ORG_ID
    if not oid:
        raise ValueError(
            "Organization ID is required. Either pass org_id parameter "
            "or set the YAPARAI_ORG_ID environment variable. "
            "Use list_organizations() to find your org ID."
        )
    return oid

Tool Definition Quality

A4.3/5.0
Behavior3/5

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

No annotations provided, so description carries the burden. It states 'No credits charged' and implies read-only by returning membership data. However, it does not discuss idempotency, rate limits, or potential side effects, which is acceptable for a simple list operation.

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?

Description is concise with 6 sentences, all providing value. 'Returns:' block structures the output clearly. No unnecessary words.

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?

For a zero-parameter list tool, the description covers purpose, output schema, cost (no credits), and practical usage tip. No obvious gaps given the simplicity.

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

Parameters4/5

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

Input schema has no parameters (100% coverage by schema), so description adds value by detailing the return fields (id, name, role, member count). This goes beyond the schema, which only provides property types.

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 'List your organizations on YaparAI' with specific verb and resource, and explains the returned data (IDs, names, role). It distinguishes from sibling list tools by focusing on organizations.

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?

Provides practical guidance: use the org ID for enterprise tools and set YAPARAI_ORG_ID env var to skip passing org_id. Does not explicitly mention when to use this tool vs alternatives, but the 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