Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

search_job_postings

Search job postings to identify companies that are hiring and discover buying signals for sales intelligence.

Instructions

Search for job postings to identify companies that are hiring and find buying signals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
q_keywordsNoKeywords to search in job postings
organization_idsNoFilter by organization IDs
pageNoPage number

Implementation Reference

  • The main handler function that performs the actual tool execution: calls Apollo API /job_postings/search endpoint with provided arguments, processes up to 20 job postings, and returns formatted text results.
    private async searchJobPostings(args: any) {
      const response = await this.axiosInstance.post("/job_postings/search", args);
      const jobPostings = response.data.job_postings || [];
    
      let result = `Job Postings Found: ${jobPostings.length}\n\n`;
    
      jobPostings.slice(0, 20).forEach((job: any, index: number) => {
        result += `${index + 1}. ${job.title}\n`;
        result += `   Company: ${job.organization?.name || "N/A"}\n`;
        result += `   Location: ${job.city || "N/A"}\n`;
        result += `   Posted: ${job.posted_at ? new Date(job.posted_at).toLocaleDateString() : "N/A"}\n`;
        result += `   URL: ${job.url || "N/A"}\n\n`;
      });
    
      return {
        content: [
          {
            type: "text",
            text: result,
          },
        ],
      };
    }
  • The input schema defining the parameters for the search_job_postings tool: q_keywords (string), organization_ids (array of strings), page (number).
    inputSchema: {
      type: "object",
      properties: {
        q_keywords: {
          type: "string",
          description: "Keywords to search in job postings",
        },
        organization_ids: {
          type: "array",
          items: { type: "string" },
          description: "Filter by organization IDs",
        },
        page: {
          type: "number",
          description: "Page number",
        },
      },
    },
  • src/index.ts:561-583 (registration)
    The tool registration object in the getTools() method, which lists available tools including search_job_postings with its name, description, and input schema.
    {
      name: "search_job_postings",
      description:
        "Search for job postings to identify companies that are hiring and find buying signals.",
      inputSchema: {
        type: "object",
        properties: {
          q_keywords: {
            type: "string",
            description: "Keywords to search in job postings",
          },
          organization_ids: {
            type: "array",
            items: { type: "string" },
            description: "Filter by organization IDs",
          },
          page: {
            type: "number",
            description: "Page number",
          },
        },
      },
    },
  • src/index.ts:96-97 (registration)
    The dispatch case in the CallToolRequestSchema handler that routes calls to the search_job_postings tool to its implementation method.
    case "search_job_postings":
      return await this.searchJobPostings(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 mentions the action ('search') and goal, but lacks critical behavioral details: it doesn't specify if results are paginated (implied by 'page' parameter but not stated), rate limits, authentication needs, or what the output looks like (no output schema). This is inadequate for a search tool with zero 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 core action ('Search for job postings') and adds value with the goal context. There is no wasted wording or redundancy, making it highly concise and well-structured.

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 tool's complexity (search functionality with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or usage constraints. The goal context ('find buying signals') is useful but insufficient to compensate for missing behavioral and output details.

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 fully documents all three parameters (q_keywords, organization_ids, page). The description adds no parameter-specific information beyond what's in the schema. According to rules, baseline is 3 when schema coverage is high (>80%) and no param info is added in the description.

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 tool's purpose: 'Search for job postings' (verb+resource). It adds context about the goal ('identify companies that are hiring and find buying signals'), which is helpful. However, it doesn't explicitly differentiate from sibling tools like 'search_organizations' or 'search_people', which prevents a score of 5.

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. It mentions the goal ('find buying signals') but doesn't specify scenarios, prerequisites, or exclusions. For example, it doesn't clarify if this is for initial prospecting versus deep analysis, or how it differs from other search tools in the server.

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