Skip to main content
Glama
lkm1developer

Apollo.io MCP Server

organization_job_postings

Find job postings for a specific organization using its Apollo.io ID to identify hiring needs and opportunities.

Instructions

Use the Organization Job Postings endpoint to find job postings for a specific organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organization_idYesApollo.io organization ID

Implementation Reference

  • Core handler function that performs the API GET request to Apollo.io's organization job postings endpoint.
    async organizationJobPostings(organizationId: string): Promise<any> {
      try {
        const url = `${this.baseUrl}/organizations/${organizationId}/job_postings`;
        const response = await this.axiosInstance.get(url);
        
        if (response.status === 200) {
          return response.data;
        } else {
          console.error(`Error: ${response.status} - ${response.statusText}`);
          return null;
        }
      } catch (error: any) {
        console.error(`Error: ${error.response?.status} - ${error.response?.statusText || error.message}`);
        return null;
      }
    }
  • MCP CallToolRequestSchema handler case that delegates to the ApolloClient method with organization_id argument.
    case 'organization_job_postings': {
      const result = await this.apollo.organizationJobPostings(args.organization_id as string);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
  • src/index.ts:172-185 (registration)
    Tool registration in ListToolsRequestSchema response, including input schema definition.
    {
      name: 'organization_job_postings',
      description: 'Use the Organization Job Postings endpoint to find job postings for a specific organization',
      inputSchema: {
        type: 'object',
        properties: {
          organization_id: { 
            type: 'string', 
            description: 'Apollo.io organization ID' 
          }
        },
        required: ['organization_id']
      }
    },
  • Input schema for the organization_job_postings tool requiring organization_id.
    inputSchema: {
      type: 'object',
      properties: {
        organization_id: { 
          type: 'string', 
          description: 'Apollo.io organization ID' 
        }
      },
      required: ['organization_id']
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool 'finds' job postings, implying a read operation, but doesn't mention permissions, rate limits, pagination, or what the response includes. This leaves significant gaps for a tool with no output schema.

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 with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list of postings, metadata), error conditions, or behavioral traits. For a tool with 1 parameter and 100% schema coverage, it minimally covers purpose but lacks critical context for 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?

Schema description coverage is 100%, so the schema already documents the 'organization_id' parameter. The description adds no additional meaning about the parameter beyond implying it's for a 'specific organization', which is redundant with the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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: 'find job postings for a specific organization' with a specific verb ('find') and resource ('job postings'). It distinguishes from siblings like 'organization_search' or 'employees_of_company' by focusing on job postings, but doesn't explicitly contrast them.

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 'organization_search' or 'people_search'. It mentions 'specific organization' but doesn't clarify prerequisites, exclusions, or comparative use cases 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/lkm1developer/apollo-io-mcp-server'

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