Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

get_account

Retrieve detailed organization information using account ID or company domain to access B2B sales intelligence data.

Instructions

Get detailed information about an account/organization by ID or domain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAccount ID
domainNoCompany domain

Implementation Reference

  • The handler function that retrieves account/organization details from Apollo API by ID or domain, formats the response as text.
    private async getAccount(args: any) {
      const endpoint = args.id
        ? `/accounts/${args.id}`
        : `/accounts/search?q_organization_domains[]=${args.domain}`;
    
      const response = await this.axiosInstance.get(endpoint);
      const account = args.id
        ? response.data.account
        : response.data.accounts?.[0];
    
      if (!account) {
        return {
          content: [
            {
              type: "text",
              text: "Account not found.",
            },
          ],
        };
      }
    
      let result = `Account Details:\n\n`;
      result += `Name: ${account.name}\n`;
      result += `ID: ${account.id}\n`;
      result += `Domain: ${account.domain || account.website_url || "N/A"}\n`;
      result += `Industry: ${account.industry || "N/A"}\n`;
      result += `Employees: ${account.estimated_num_employees || "N/A"}\n`;
      result += `Phone: ${account.phone || "N/A"}\n`;
    
      return {
        content: [
          {
            type: "text",
            text: result,
          },
        ],
      };
    }
  • src/index.ts:543-560 (registration)
    Registers the get_account tool in the tools list, including its name, description, and input schema.
    {
      name: "get_account",
      description:
        "Get detailed information about an account/organization by ID or domain.",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "Account ID",
          },
          domain: {
            type: "string",
            description: "Company domain",
          },
        },
      },
    },
  • Defines the input schema for the get_account tool, accepting id or domain.
    inputSchema: {
      type: "object",
      properties: {
        id: {
          type: "string",
          description: "Account ID",
        },
        domain: {
          type: "string",
          description: "Company domain",
        },
      },
    },
  • Switch case in the main CallToolRequest handler that dispatches to the getAccount method.
    case "get_account":
      return await this.getAccount(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it 'gets' information, implying a read-only operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling, or what 'detailed information' includes. This leaves significant gaps for a tool with no annotation coverage.

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, efficient sentence that front-loads the purpose without unnecessary words. It directly communicates the tool's function and parameters, making it easy to parse quickly.

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 the complexity of account/organization data, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'detailed information' entails, potential response formats, or error cases. For a read operation with rich data likely returned, more context is needed to guide effective use.

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?

The schema description coverage is 100%, with clear descriptions for 'id' and 'domain'. The description adds minimal value by mentioning these parameters as lookup methods ('by ID or domain'), but doesn't provide additional semantics like format examples or usage constraints beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 an account/organization'), specifying it retrieves data by ID or domain. However, it doesn't differentiate from sibling tools like 'search_organizations' or 'enrich_organization', which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives like 'search_organizations' or 'enrich_organization'. It mentions the lookup methods (ID or domain) but doesn't specify prerequisites, exclusions, or comparative contexts with sibling tools.

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/masridigital/apollo.io-mcp'

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