Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

get_person_activity

Retrieve engagement history and activity data for Apollo.io contacts to analyze interactions and track communication patterns.

Instructions

Get activity history and engagement data for a specific person/contact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPerson/Contact ID

Implementation Reference

  • The core handler function that fetches the person's activity history from the Apollo.io API endpoint `/people/{id}/activities`, processes the activities array, formats a textual summary with type, date, and details for each activity, handles empty results, and returns a standardized MCP content response.
    private async getPersonActivity(args: any) {
      const response = await this.axiosInstance.get(`/people/${args.id}/activities`);
      const activities = response.data.activities || [];
    
      let result = `Activity History:\n\n`;
    
      activities.forEach((activity: any, index: number) => {
        result += `${index + 1}. ${activity.type}\n`;
        result += `   Date: ${activity.created_at ? new Date(activity.created_at).toLocaleDateString() : "N/A"}\n`;
        result += `   Details: ${activity.note || "N/A"}\n\n`;
      });
    
      if (activities.length === 0) {
        result += "No activity found for this contact.\n";
      }
    
      return {
        content: [
          {
            type: "text",
            text: result,
          },
        ],
      };
    }
  • Defines the input validation schema for the tool, requiring a single 'id' property of type string representing the Person/Contact ID.
    inputSchema: {
      type: "object",
      properties: {
        id: {
          type: "string",
          description: "Person/Contact ID",
        },
      },
      required: ["id"],
    },
  • src/index.ts:584-598 (registration)
    Registers the tool in the getTools() method with its name, description, and input schema for the MCP server.
    {
      name: "get_person_activity",
      description:
        "Get activity history and engagement data for a specific person/contact.",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "Person/Contact ID",
          },
        },
        required: ["id"],
      },
    },
  • src/index.ts:98-99 (registration)
    The switch case dispatcher in the main tool handling method that routes calls to the specific getPersonActivity handler.
    case "get_person_activity":
      return await this.getPersonActivity(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. It states the tool retrieves data ('Get'), implying it is read-only, but does not clarify permissions, rate limits, data format, or whether it returns historical or real-time data. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that efficiently conveys the core purpose without unnecessary details. It is front-loaded and wastes no words, making it easy to parse. However, it could be slightly improved by adding brief usage context without losing conciseness.

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 lack of annotations and output schema, the description is incomplete. It does not explain what 'activity history and engagement data' includes, how results are structured, or any limitations. For a tool that retrieves potentially complex data, more context is needed to help an agent use it effectively.

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 input schema has 100% description coverage, with the 'id' parameter documented as 'Person/Contact ID'. The description adds minimal value beyond this, as it only reiterates that the tool is for a 'specific person/contact'. Since the schema already covers the parameter semantics adequately, the baseline score of 3 is appropriate.

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: 'Get activity history and engagement data for a specific person/contact.' It specifies the verb ('Get'), resource ('activity history and engagement data'), and target ('specific person/contact'). However, it does not explicitly distinguish this from sibling tools like 'get_account' or 'get_sequence', which also retrieve data but for different resources.

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 does not mention prerequisites, such as needing a valid person ID, or compare it to sibling tools like 'search_people' for finding people or 'enrich_person' for additional data. Without this context, an agent might struggle to select the right tool.

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