Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

search_organizations

Find companies in Apollo.io's database by filtering industry, size, location, revenue, technology, and keywords to build targeted account lists.

Instructions

Search for companies/organizations in Apollo's database. Filter by industry, size, location, revenue, technology, and more. Great for building targeted account lists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
q_organization_nameNoOrganization name search
organization_locationsNoLocations (e.g., ["San Francisco, CA"])
organization_industry_tag_idsNoIndustry tag IDs
organization_num_employees_rangesNoEmployee count ranges: "1-10", "11-50", "51-200", "201-500", "501-1000", "1001-5000", "5001-10000", "10001+"
revenue_rangeNoRevenue range filter
organization_keywordsNoKeywords to search in organization data
pageNoPage number (default: 1)
per_pageNoResults per page (default: 25, max: 100)

Implementation Reference

  • The handler function for search_organizations tool. Makes API call to Apollo's /mixed_companies/search endpoint with provided args, formats the organizations data into a readable text summary including pagination, ID, name, domain, industry, employees, location, revenue, and phone.
    private async searchOrganizations(args: any) {
      const response = await this.axiosInstance.post("/mixed_companies/search", args);
      const organizations = response.data.organizations || [];
      const pagination = response.data.pagination || {};
    
      let result = `Found ${pagination.total_entries || organizations.length} organizations\n`;
      result += `Page ${pagination.page || 1} of ${pagination.total_pages || 1}\n\n`;
    
      organizations.forEach((org: any, index: number) => {
        result += `${index + 1}. ${org.name}\n`;
        result += `   ID: ${org.id}\n`;
        result += `   Domain: ${org.website_url || org.primary_domain || "N/A"}\n`;
        result += `   Industry: ${org.industry || "N/A"}\n`;
        result += `   Employees: ${org.estimated_num_employees || "N/A"}\n`;
        result += `   Location: ${org.city ? `${org.city}, ${org.state || org.country}` : "N/A"}\n`;
        result += `   Revenue: ${org.annual_revenue ? `$${org.annual_revenue}` : "N/A"}\n`;
        result += `   Phone: ${org.phone || "N/A"}\n\n`;
      });
    
      return {
        content: [
          {
            type: "text",
            text: result,
          },
        ],
      };
    }
  • Input schema for the search_organizations tool defining parameters such as organization name query, locations, industry tags, employee ranges, revenue range, keywords, pagination.
    inputSchema: {
      type: "object",
      properties: {
        q_organization_name: {
          type: "string",
          description: "Organization name search",
        },
        organization_locations: {
          type: "array",
          items: { type: "string" },
          description: 'Locations (e.g., ["San Francisco, CA"])',
        },
        organization_industry_tag_ids: {
          type: "array",
          items: { type: "string" },
          description: "Industry tag IDs",
        },
        organization_num_employees_ranges: {
          type: "array",
          items: { type: "string" },
          description:
            'Employee count ranges: "1-10", "11-50", "51-200", "201-500", "501-1000", "1001-5000", "5001-10000", "10001+"',
        },
        revenue_range: {
          type: "object",
          properties: {
            min: { type: "number" },
            max: { type: "number" },
          },
          description: "Revenue range filter",
        },
        organization_keywords: {
          type: "array",
          items: { type: "string" },
          description: "Keywords to search in organization data",
        },
        page: {
          type: "number",
          description: "Page number (default: 1)",
        },
        per_page: {
          type: "number",
          description: "Results per page (default: 25, max: 100)",
        },
      },
    },
  • src/index.ts:171-221 (registration)
    Tool registration in the getTools() method's return array, including name, description, and inputSchema.
    {
      name: "search_organizations",
      description:
        "Search for companies/organizations in Apollo's database. Filter by industry, size, location, revenue, technology, and more. Great for building targeted account lists.",
      inputSchema: {
        type: "object",
        properties: {
          q_organization_name: {
            type: "string",
            description: "Organization name search",
          },
          organization_locations: {
            type: "array",
            items: { type: "string" },
            description: 'Locations (e.g., ["San Francisco, CA"])',
          },
          organization_industry_tag_ids: {
            type: "array",
            items: { type: "string" },
            description: "Industry tag IDs",
          },
          organization_num_employees_ranges: {
            type: "array",
            items: { type: "string" },
            description:
              'Employee count ranges: "1-10", "11-50", "51-200", "201-500", "501-1000", "1001-5000", "5001-10000", "10001+"',
          },
          revenue_range: {
            type: "object",
            properties: {
              min: { type: "number" },
              max: { type: "number" },
            },
            description: "Revenue range filter",
          },
          organization_keywords: {
            type: "array",
            items: { type: "string" },
            description: "Keywords to search in organization data",
          },
          page: {
            type: "number",
            description: "Page number (default: 1)",
          },
          per_page: {
            type: "number",
            description: "Results per page (default: 25, max: 100)",
          },
        },
      },
    },
  • src/index.ts:64-65 (registration)
    Dispatch case in the CallToolRequestSchema handler switch statement that routes calls to search_organizations to the searchOrganizations method.
    case "search_organizations":
      return await this.searchOrganizations(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 of behavioral disclosure. While it mentions the tool is for searching and filtering, it lacks critical behavioral details such as whether this is a read-only operation, what permissions are required, rate limits, pagination behavior beyond the schema's default values, or what the response format looks like. For a search tool with 8 parameters and no annotations, this is a significant gap.

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 efficiently structured in two sentences: the first states the purpose and key capabilities, and the second provides usage context. Every sentence earns its place with no wasted words, making it easy to scan and understand quickly.

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 tool's complexity (8 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the purpose and high-level usage well, but lacks behavioral transparency details and doesn't compensate for the missing output schema. For a search tool with rich filtering options, more context on result format or limitations would be helpful.

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 schema already documents all 8 parameters thoroughly. The description adds marginal value by listing example filter categories ('industry, size, location, revenue, technology, and more'), but doesn't provide additional syntax, format details, or usage examples beyond what the schema provides. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Search for companies/organizations') and resource ('Apollo's database'), with explicit mention of filtering capabilities. It distinguishes this tool from sibling tools like 'search_people' and 'search_job_postings' by specifying its focus on organizations rather than individuals or job postings.

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 provides clear context for when to use this tool ('Great for building targeted account lists'), which implicitly suggests it's for prospecting or lead generation. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools, such as when to use 'enrich_organization' instead.

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